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
Now that we have made resource classes optional, we should move this setting to the schema's relation field. That would mean we could use it both when serializing the relation and when registering routes. (To use it when serializing relations we would need to always inject the schema into the resource class - even if using a specific resource class e.g. PostResource.)
The text was updated successfully, but these errors were encountered:
At the moment, if you want to use a different convention for a relationship's URI, you have to define it in two places.
Firstly, when registering the route:
Secondly, on the resource's relation object:
Now that we have made resource classes optional, we should move this setting to the schema's relation field. That would mean we could use it both when serializing the relation and when registering routes. (To use it when serializing relations we would need to always inject the schema into the resource class - even if using a specific resource class e.g.
PostResource
.)The text was updated successfully, but these errors were encountered: