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

Does a statebus implementation require "eval"? #47

Open
floer32 opened this issue Aug 14, 2021 · 2 comments
Open

Does a statebus implementation require "eval"? #47

floer32 opened this issue Aug 14, 2021 · 2 comments

Comments

@floer32
Copy link

floer32 commented Aug 14, 2021

The current codebase has some eval (and dynamically evaluated CoffeeScript). I started playing with the code to see if I could remove the need for this. Is that misguided — is there no way around it?

@toomim
Copy link
Member

toomim commented Aug 14, 2021

No no, it doesn't require coffeescript or eval. Those are just a set of handy routines in client.js that you can use if you want. But you can totally ignore them, and in fact you can completely ignore client.js if you want. That stuff is all built on the inner statebus.js code.

You can think of client.js and server.js as "a collection of common ways to use statebus.js." The client.js code shows you how to integrate it really nicely with React and even Coffeescript over a network, but you can ignore it if you want to get lower-level.

More info at #46

@floer32
Copy link
Author

floer32 commented Aug 15, 2021

You can think of client.js and server.js as "a collection of common ways to use statebus.js."

Good sentence to add to the quickstart, maybe?

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

2 participants