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
{{ message }}
This repository has been archived by the owner on Sep 24, 2018. It is now read-only.
My Post Resource shouldn't need to know of the route to the User Resource. My Post Resource be able to return the relationship in a structured manner, and have the Server resolve the proper route.
We've discussed this ad-naseum, and no good solution has presented itself. Registry is one challenge. Resolving a Resource route based on its regex and ID would require creating a library — ick.
For now, let's "hardcode" these links. When hardcoding becomes an actual problem, we can re-address.
As a core endpoint author, I'd like to be able to embed a reference to a User (e.g. author) from my Post.
Currently, this relationship is strongly coupled:
My Post Resource shouldn't need to know of the route to the User Resource. My Post Resource be able to return the relationship in a structured manner, and have the Server resolve the proper route.
Related #559, #577
The text was updated successfully, but these errors were encountered: