-
Notifications
You must be signed in to change notification settings - Fork 138
Inverse relation unlink bug #383
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
Closed
Closed
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
aaf9f2c
belongsTo errors without inverse relation
pik 50fc330
Fix belongsTo error without inverse relationship
pik 7d05e20
Move safeSetProp, safeSetLink to utils
pik cd3a0bb
Fix inverseRelationUnlink Bug (sort of)
pik 673bf76
remove debug logging
pik File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -156,18 +156,14 @@ utils.addHiddenPropsToTarget(Relation.prototype, { | |
const localField = this.localField | ||
records.forEach((record) => { | ||
const relatedData = utils.get(record, localField) | ||
this.unlinkInverseRecords(relatedData) | ||
/* CAN DEPRECATE? */ | ||
// this.unlinkInverseRecords(relatedData, record) | ||
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is code-reduplicative and incorrect for many cases (also only used in 1 place), optimally there should only be 1 standard correct method called for all pathways which need to unlink. |
||
|
||
// descriptor.set will trigger removeInverseRelations | ||
utils.set(record, localField, undefined) | ||
}) | ||
}, | ||
|
||
unlinkInverseRecords (record) { | ||
if (!record) { | ||
return | ||
} | ||
utils.set(record, this.getInverse(this.mapper).localField, undefined) | ||
}, | ||
|
||
linkRecord (record, relatedRecord) { | ||
const relatedId = utils.get(relatedRecord, this.mapper.idAttribute) | ||
|
||
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Formerly the above
// Update (unset) inverse relation
would only get called on update not onclear/delete
. I addedsafeSetLink(current, inverseLocalField, undefined)
which fixes the broken destroy test.On the other-hand attempting to add
safeSetProp(current, foreignKey, undefined)
(commented out below) which should make sense (Why would we keep foreign keys after clearing the relation?) causes 4 other specs to break in the collection_methods suite.