Open fisherwebdev opened 10 years ago
or should I submit a PR now (or the next day or two) and let Flux become one of the first compile-to-JS projects?
I would be ok with that.
// @tastejs/owners
I'd be very happy to see a proper Flux example. We are going to change the transpiler rule very shortly anyway. On Sep 16, 2014 6:17 PM, "Sindre Sorhus" notifications@github.com wrote:
or should I submit a PR now (or the next day or two) and let Flux become one of the first compile-to-JS projects?
I would be ok with that.
// @tastejs/owners https://github.com/orgs/tastejs/teams/owners
— Reply to this email directly or view it on GitHub https://github.com/tastejs/todomvc/issues/998#issuecomment-55778038.
As I said on Twitter, I'm more than happy for a Flux implementation to land. Also happy for us to relax the rules around transpilers (@passy is going to update them soon).
I see that there is some movement toward including projects that rely on a transpile step, with TasteLang in issue #945. I'd very much like to submit a Flux TodoMVC example that includes the use of React's JSX syntax, as this has been the canonical way of writing Flux apps and the existing Flux community is moving in that direction. Should I wait to submit Flux until these issues are resolved, or should I submit a PR now (or the next day or two) and let Flux become one of the first compile-to-JS projects?
I think submitting Flux with a Vanilla JS implementation would actually confuse newcomers to the Flux community more than I'd like.
To see the current state of our TodoMVC Flux implementation, check out the Flux repo: https://github.com/facebook/flux/tree/master/examples/flux-todomvc