Hi,
first of all thanks for the great work!
We are experiencing inconsistent assignments of id attributes inside linked/associated resource.
Here is an example of an award resource that has an associated ad resource. You can see that the id attribute is sometimes the actual id and other times the permalink. This creates problems on our backend when we do update operations on a resource, since the backend never know by what to query the associated resources (permalink or id).
Examples:
permalink inside id attribute of linked resource
{
"data": {
"id": "4200-rock-deodorant",
"state": "assigned",
"links": {
"ad": {
"linkage": {
"id": "too-much-game",
"type": "ads"
}
}
},
"type": "awards"
}
}
actual ID inside the id attribute of linked ad resource
{
"data": {
"id": "4200-rock-deodorant",
"state": "assigned",
"links": {
"ad": {
"linkage": {
"id": "10656",
"type": "ads"
}
}
},
"type": "awards"
}
}
Hi,
first of all thanks for the great work!
We are experiencing inconsistent assignments of
idattributes inside linked/associated resource.Here is an example of an
awardresource that has an associatedadresource. You can see that theidattribute is sometimes the actualidand other times thepermalink. This creates problems on our backend when we do update operations on a resource, since the backend never know by what to query the associated resources (permalinkorid).Examples:
permalinkinsideidattribute of linked resourceactual ID inside the
idattribute of linked ad resource