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

[BUGFIX] update content of proxy for async belongs-to relationships when null data received #5461

Merged

Conversation

fivetanley
Copy link
Member

@fivetanley fivetanley commented Apr 30, 2018

resolves #5452
replaces #5457

This adds a failing test that a relationship should disassociate records
on both sides of the relationship when a payload explicitly returns null
for the data of that relationship.

'book removed from author' is the assertion that fails here. e.g. the record is not removed on the hasMany side.

@fivetanley fivetanley force-pushed the figuring-out-nulling-relationship-by-returning-empty-payload branch from d435dc9 to 98bda33 Compare April 30, 2018 21:39
This adds a failing test that a relationship should disassociate records
on both sides of the relationship when a payload explicitly returns null
for the data of that relationship.
@fivetanley fivetanley force-pushed the figuring-out-nulling-relationship-by-returning-empty-payload branch from 98bda33 to 741fe77 Compare April 30, 2018 21:40
…tes content when new content is explicitly null
@runspired runspired changed the title failing test for relationships not updating when null data returned [BUGFIX] update content of proxy for async belongs-to relationships when null data received Apr 30, 2018
@runspired runspired merged commit 5b33009 into master Apr 30, 2018
@runspired runspired deleted the figuring-out-nulling-relationship-by-returning-empty-payload branch April 30, 2018 23:17
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.

Clearing a belongsTo relationship using the JSON-API seems to be broken in 3.2.0-beta.2
2 participants