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
I'm wondering if we should be setting the Content-Type response header for JsonapiErrorable#handle_exception and JsonapiErrorable::Validatable#render_errors_for. In our app we've overwritten those two methods in our base API controller to look something like this:
# Override JsonapiErrorable#handle_exception to ensure correct content typedefhandle_exception(*)self.content_type ||= Mime[:jsonapi]superendprivate# Override JsonapiErrorable::Validatable to ensure correct content typedefrender_errors_for(*)self.content_type ||= Mime[:jsonapi]superend
Ah! Sorry I think you are saying - jsonapi-rails is handling this for normal responses, but since we avoid that gem for errors we should do it here too. Is that right? If so I agree, let's do it.
@richmolj Yes, the later. jsonapi-rails is setting the Content-Type for most responses, so we get that "for free." But since we're not using that gem for error responses, the response header is not being set.
I'm wondering if we should be setting the
Content-Type
response header forJsonapiErrorable#handle_exception
andJsonapiErrorable::Validatable#render_errors_for
. In our app we've overwritten those two methods in our base API controller to look something like this:Here we're relying on the
Mime::Type
being registered - which we're getting by way ofjsonapi-rails
, which registers it in their Railtie. https://github.com/jsonapi-rb/jsonapi-rails/blob/14a9421658495fe916ec1886834b6adfd764b211/lib/jsonapi/rails/railtie.rb#L34-L36But this gem could do something similar. Is there a reason not to?
The text was updated successfully, but these errors were encountered: