Skip to content
This repository has been archived by the owner on Jan 26, 2021. It is now read-only.

return a null object state from resolveMutation when a Destroy was issued #23

Closed

Conversation

jsierles
Copy link

This fixes #14. Not sure if this was the intended behavior, but perhaps it can help fix this bug. It makes developing tedious if you're testing deletes from a list of items.

@andrewimm
Copy link
Contributor

Appreciate the PR. Unfortunately, this will not work when there are other, pending mutations on the stack -- the Destroy needs to be properly merged into them, and the results need to be committed to the true state if the stack is completely compressed.

A fix for #14 is coming with the v0.2 release, which should be out within the next day or so.

@jsierles
Copy link
Author

Glad to hear it, sorry for not checking it more thoroughly.

@jsierles jsierles closed this Apr 21, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

StackTrace after using ParseReact.Mutation.Destroy
3 participants