-
Notifications
You must be signed in to change notification settings - Fork 195
New issue
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
3.6.6 breaks deep relations #223
Comments
I have hit the same issue, and it appears to be a problem with how the code is detecting recursive relationships. If any of the parents have types that are a substring of the child type they will be detected as a recursive relation e.g. from your example because elements-layouts-profiles contains the string elements it won't keep parsing relations. To work around this, in deserializer utils I have updated the check to look at type and id instead of just type when detecting a recursion. ...
function findIncluded(relationshipData, ancestry) {
...
if (included) {
// To prevent circular references, check if the record type
// has already been processed in this thread
if (ancestry.indexOf(included.type + included.id) > -1) {
... |
up |
1 similar comment
up |
I noticed I never replied to this, but still thanks @danielpigott. We distribute this package onto our servers automatically so for now we're still on 3.6.5 since the issue doesn't occur there. It would be nice if this issue could be fixed in a future version so we can use the newest package. |
3.6.6 does not include relations deeper than the third level anymore. This worked in 3.6.5.
Expected result
Actual result
Data
The text was updated successfully, but these errors were encountered: