Skip to content

fix: correctly check for unique relation updates#355

Merged
kettanaito merged 5 commits intomainfrom
fix/incorrect-unique-check-on-update
Apr 19, 2026
Merged

fix: correctly check for unique relation updates#355
kettanaito merged 5 commits intomainfrom
fix/incorrect-unique-check-on-update

Conversation

@kettanaito
Copy link
Copy Markdown
Member

@kettanaito kettanaito commented Apr 19, 2026

Changes

  • Add missing uniqueness check when updating a referenced record.
  • Guard against updating irrelevant records when an update to a relational record is triggered.

@kettanaito kettanaito merged commit fa1c709 into main Apr 19, 2026
1 check passed
@kettanaito kettanaito deleted the fix/incorrect-unique-check-on-update branch April 19, 2026 12:56
@kettanaito
Copy link
Copy Markdown
Member Author

Released: v1.1.3 🎉

This has been released in v1.1.3.

Get these changes by running the following command:

npm i @msw/data@latest

Predictable release automation by Release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Failed to update a unique relation at "relation name": the foreign record is already associated with another owner

1 participant