fix(pinia-orm): Two same belongsToMany with inverse keys on same model are causing wrong saved data
#1860
Conversation
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
…g wrong saved data on same model
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1860 +/- ##
=======================================
Coverage 99.76% 99.76%
=======================================
Files 88 88
Lines 6032 6032
Branches 512 512
=======================================
Hits 6018 6018
Misses 12 12
Partials 2 2 ☔ View full report in Codecov by Sentry. |
CodeDredd
changed the title
belongsToMany with inverse keys are causing wrong saved data on same modelbelongsToMany with inverse keys on same model are causing wrong saved data
Merged
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
🔗 Linked issue
resolves #1857
📚 Description
This edge case is causing wrong saved data if defined on the same model:
... retailers: this.belongsToMany(Client, ClientRetailer, 'supplierId', 'retailerId'), suppliers: this.belongsToMany(Client, ClientRetailer, 'retailerId', 'supplierId'), ...