[BUGFIX] New test and possible fix for issue #7265 (self-referent rel) #7266
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This addresses issue #7265 (Self-Referent Relationship in Save Response Blows Up Save).
It includes a new test that replicates the problem - saving a record, and having the 'backend' return a relationship that is self-referent, thus blowing up Ember Data when it checks to see if the just-saved id has already been used. (Said id was added to the store as part of the relationships-handling.)
It also includes a patch to record-data.ts that solves the problem in the test, and does not cause any other tests to fail. HOWEVER, it does this by simply re-ordering the handling of relationships and the 'set the record id' call - I don't know if there is a reason that they were done in the opposite order originally, and thus don't know for certain if this will break something else. (I'm hoping the tests would have shown that, but perhaps wiser eyes can take a look to make certain.)
Thanks!