We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Say, I have resource structure like this:
{ "data": [ { "type": "news", "id": "item1", "attributes": { "title": "item1" }, "relationships": { "also": { "data": [{ "type": "news", "id": "item2" }] } } }, { "type": "news", "id": "item2", "attributes": { "title": "item2" }, "relationships": { "also": { "data": [{ "type": "news", "id": "item3" }] } } } ] }
And I want to get resources like this:
{ "data": [ { "type": "news", "id": "item1", "attributes": { "title": "item1" }, "relationships": { "also": { "data": [{ "type": "news", "id": "item2" }] } } }, { "type": "news", "id": "item2", "attributes": { "title": "item2" }, "relationships": { "also": { "data": [{ "type": "news", "id": "item3" }] } } } ], "included": [ { "type": "other_companies", "id": "item2", "attributes": { "title": "item2", "link": "link", "code": "item2", ... } } ] }
For now there will be triggered error "can not have multiple resources with the same identification".
Can we add individual id validation for included? Just make another claimUsedResourceIdentifier for included. Or add option for validator.
id
included
claimUsedResourceIdentifier
The text was updated successfully, but these errors were encountered:
not relevant
Sorry, something went wrong.
No branches or pull requests
Say, I have resource structure like this:
And I want to get resources like this:
For now there will be triggered error "can not have multiple resources with the same identification".
Can we add individual
id
validation forincluded
?Just make another
claimUsedResourceIdentifier
forincluded
.Or add option for validator.
The text was updated successfully, but these errors were encountered: