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

StackTrace after using ParseReact.Mutation.Destroy #14

Closed
nivoc opened this issue Apr 8, 2015 · 8 comments
Closed

StackTrace after using ParseReact.Mutation.Destroy #14

nivoc opened this issue Apr 8, 2015 · 8 comments

Comments

@nivoc
Copy link

nivoc commented Apr 8, 2015

image

The content of the mentioned variable in the trace is a string "DESTORY". And that breaks var changed = Object.keys(delta.map);

(Updated description and headline - first was wrong lead)

@nivoc
Copy link
Author

nivoc commented Apr 8, 2015

Umpf. No my solution is wrong. I will have to dive deeper to find the real cause :-(

@andrewimm
Copy link
Contributor

Interesting. I'll take a deeper look at this as soon as I can. We actually are planning on moving to immutable-js, but that's some time down the road.

@nivoc
Copy link
Author

nivoc commented Apr 8, 2015

Found it - But not sure why jet.

The content of the mentioned variable in the trace is a string "DESTORY". And that breaks var changed = Object.keys(delta.map);

@andrewimm
Copy link
Contributor

Just sounds like a bug on my part. I'll have a fix out later tonight.

@nivoc nivoc changed the title React Native's ListView breaks if used with ParseReact because it expects immutables StackTrace after using ParseReact.Mutation.Destroy Apr 8, 2015
@nivoc
Copy link
Author

nivoc commented Apr 8, 2015

Thanks

@nivoc nivoc closed this as completed Apr 8, 2015
@nivoc nivoc reopened this Apr 8, 2015
@nivoc
Copy link
Author

nivoc commented Apr 8, 2015

Note: It does not happen in my app if the debug-window is open.

@jsierles
Copy link

Same experience here.

@andrewimm
Copy link
Contributor

v0.2.0 is out, this should be resolved.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants