Skip to content
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

Added failing test for #5136. #5137

Closed
wants to merge 1 commit into from

Conversation

workmanw
Copy link

@workmanw workmanw commented Aug 17, 2017

@workmanw workmanw force-pushed the failing-test-for-5136 branch from cf265c8 to 1e41ea7 Compare December 1, 2017 22:02
hjdivad added a commit that referenced this pull request Jan 11, 2018
A number of use cases rely on unloadRecord's 2.12 behaviour of treating
unloadRecord as a client-side delete on the inverse side of a sync
relationship.

This pr restores that functionality, while retaining the
invalidate+refetch functionality for async relationships.

This behaviour is codified in a number of tests within
tests/integration/records/unload-test.js

Fix #5136, #5137
@hjdivad
Copy link
Member

hjdivad commented Jan 11, 2018

closed by #5273

@hjdivad hjdivad closed this Jan 11, 2018
bmac pushed a commit that referenced this pull request Feb 13, 2018
A number of use cases rely on unloadRecord's 2.12 behaviour of treating
unloadRecord as a client-side delete on the inverse side of a sync
relationship.

This pr restores that functionality, while retaining the
invalidate+refetch functionality for async relationships.

This behaviour is codified in a number of tests within
tests/integration/records/unload-test.js

Fix #5136, #5137

(cherry picked from commit 6e8a236)
mcfiredrill pushed a commit to mcfiredrill/data that referenced this pull request Feb 15, 2018
A number of use cases rely on unloadRecord's 2.12 behaviour of treating
unloadRecord as a client-side delete on the inverse side of a sync
relationship.

This pr restores that functionality, while retaining the
invalidate+refetch functionality for async relationships.

This behaviour is codified in a number of tests within
tests/integration/records/unload-test.js

Fix emberjs#5136, emberjs#5137

(cherry picked from commit 6e8a236)
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.

2 participants