Added failing test: "Fetching a belongsTo that is set to null removes the record from a relationship - sync - and do it twice" #9326
Conversation
This file contains 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
…ord from a relationship - sync - and do it twice
runspired
added
🎯 canary
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.
This is a PR to facilitate the fixing of #8990.
An extra test "Fetching a belongsTo that is set to null removes the record from a relationship - sync - and do it twice", has been added.
Description
It is actually the same test as the existing one that precedes it: "Fetching a belongsTo that is set to null removes the record from a relationship - sync" but only run twice immediately after each other.
If the user.accounts are not accessed in between (see the assert.strictEqual - put in comment), the test fails, otherwise the test succeeds.