destroyed objects rendering about jsonapi_compliable

[richmolj]

I'm not totally opposed to adding "out of the box" support, but currently I think users can do this on their own:

def destroy
  post = Post.find(1)
  if post.destroy
    render jsonapi: nil, meta: { foo: 'bar' }, status: 200
    # or
    return head(:no_content)
  else
    render_errors_for(post)
  end
end

Would that work for you?

[klobuczek]

Yes. That's what I ended up doing. I was just confused since the documentation suggested calling render_jsonapi on the destroyed object which is the rails way, but I could not find anything corresponding in the code.

[richmolj]

Yep, I think it's really whether or not you prefer the Rails default or pure compliance. The docs could definitely be improved here.

[daniel-sullivan]

Just in case anyone comes across this via Google (it's the top result for 'render_jsonapi status', it is possible to set the return status from the render_jsonapi method itself by:

render_jsonapi company, scope: false, status: 201

It's not possible to use: render jsonapi: company, status: 201 if you are relying on the @context variable in any of your serializers as this is set and passed by render_jsonapi