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
Nah, this takes the approach of transforming simpler fields - often hyperlink strings or PK ints - into complex, nested objects. Looks like JSON API instead appends the related objects in an included field.
There is this project, which offers some level of support for JSON API -- not sure about its support for dynamic embedding.
My (small) team prefers the direct expansion approach; see Stripe for an example of a major API that does same. Though, if you're working on a larger team, I can definitely see benefit of looking to a well-documented standard like JSON API, rather than trying to come up with and standardize on your own spec.
Thanks for the clarification @rsinger86 I still need to think more about it. If you and Stripe prefer the direct expansion approach, there's must be a good reason for it.
I cannot tell but does this conform to jsonapi.org specification on how to render the JSON format?
The text was updated successfully, but these errors were encountered: