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

Flux Constants #137

Closed
travisperson opened this issue Sep 30, 2015 · 1 comment
Closed

Flux Constants #137

travisperson opened this issue Sep 30, 2015 · 1 comment

Comments

@travisperson
Copy link

Has anyone used this with something like Flux Constants? I'm curious how the concept of an type being an object will work into a tool like this. I could see it handling it no issue. Though I also see an issue when it comes to serializing state and actions. Specificity if I wanted to download and reload my application with a particular state, and a set of action to play through. Since with flux constant you are dealing with objects and not strings, you'd some how need to match the object in the action back up with the actual object reference at run time.

I like the idea behind flux-constants but I don't like the idea of distancing myself from the tools and other amazing things that Redux gives from it's simplicity.

@travisperson
Copy link
Author

After reading through this issue (reduxjs/redux#786) and playing around with flux constants and the todo example I've concluded that using flux-constants or anything like it does not work.

It primarily comes down to the issue that you can not serialize object references correctly. To make sure you don't loose out on some amazing tools I think serializing state and action frequencies is very important.

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

No branches or pull requests

1 participant