You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The `PublicExceptions` middleware is used on _every_ request. It doesn't
make sense to create JSON API specific request objects for requests that
are _not_ part of a JSON API route. Instead we should only create those
requests _after_ we've already confirmed we are working with a JSON API
request.
Along these lines we should only be checking the path to see if it is a
pre-determined JSON API resource. Further mime type negotiation /
validation should be handled by the final endpoint. I'm not sure why we
did the format check here initially; I can only think that it was meant
to be more "generic" and possibly allow multiple content types but only
wrap errors for JSON API content. However, our current endpoints are
JSON API only and clients would likely expect JSON API errors for any
problems when accessing them.
0 commit comments