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
Right now jsonApiType is using for resource type and in URI builder. But in JSON:API specification there is no rule to keep them same.
Example:
I have resource with type: "Truck", but it's listed in GET /cars endpoint.
I propose to have extra property which will be used in URI path. If it's value is undefined or null - then jsonApiType will be used as it's working now.
The text was updated successfully, but these errors were encountered:
Right now
jsonApiType
is using for resourcetype
and in URI builder. But in JSON:API specification there is no rule to keep them same.Example:
I have resource with
type: "Truck"
, but it's listed inGET /cars
endpoint.I propose to have extra property which will be used in URI path. If it's value is
undefined
ornull
- thenjsonApiType
will be used as it's working now.The text was updated successfully, but these errors were encountered: