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
Unfortunately this is by design. We follow the specification and that disallows attributes and relationships with the same name.
Fields for a resource object MUST share a common namespace with each other and with type and id. In other words, a resource can not have an attribute and relationship with the same name, nor can it have an attribute or relationship named type or id.
The response from the API has attributes that are the same name as an included resource.
Detailed description
The response from the API has attributes that are the same name as an included resource:
Where
sales
can also be an optional include.This causes an error stating:
Relationship "xxx" cannot be set because it already exists in Resource object.
My question is if this is a known issue, something that can be wroked around or just going to be a problem for me using this package?
The text was updated successfully, but these errors were encountered: