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
Sorry to piggyback on this issue, but I figured this would be an appropriate place for this question.
We are currently using ams, but have run into some snags with rendering relationships properly. We want to move away from ams but we will have to do it in passes. AMS at the moment is integrated heavily in both, controller rendering and as standalone using AMS::SerializableResource with action cable.
We would like to start by replacing one serializer at a time.
Good news: jsonapi-rb uses different class names so no conflict with ams
Bad news: I see that both ams and jsonapi-rb use the same render :jsonapi construct for rendering. Is there a way in which we can make jsonapi-rb use another method? Or are we thinking about this completely the wrong way?
Identified gotchas:
attribute :foo, key: :bar
: in AMS, this creates abar
attribute in the JSON output. In jsonapi-rb, this becomesattribute(:bar) { @object.foo }
.The text was updated successfully, but these errors were encountered: