Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Dan Weaver
    @dan-weaver
    or is anyone working on a port
    Dan Weaver
    @dan-weaver
    never mind I wrote my own
    Raul Matei
    @raulmatei
    @dweave, @jordangarcia has something here: https://github.com/jordangarcia/nuclear-router
    Umut Sirin
    @usirin
    Hello guys, can you checkout #201 and give feedback if possible please?
    Raul Matei
    @raulmatei
    @usirin 👍
    jma7889
    @jma7889
    Hello, I am new to flux engine, though I have been using react for a while with react-router. Now I want to add flux pattern, I am choosing between redux and nuclear-js. Which one is easier to use? Does nuclear-js work together with react-router well?
    Dan Weaver
    @dan-weaver
    @jma7889 Personally I haven't found a flux implementation that works especially well with react router.
    I'm sort of a beginner to flux as well and have used both redux and nuclear and find that they are about equal when it comes to router.
    I'm not on the nuclear team just FYI
    i did find nuclear easier to understand initially, as long as ur comfortable with immutablejs
    jma7889
    @jma7889
    @dweave Thanks. Redux-simple-router integrate both well. But somehow I feel there's more plumbing work when using redux. I feel they trade off some usability for extendability. For me, I only care about under my environment, don't care about if it can be used with Angular, or other immutable libs.
    Dan Weaver
    @dan-weaver
    yeah. More glue needed for redux in my opinion. Redux simple router looks good, but as the name suggests it's very simple lol
    just persists the URL basically
    if your into using normal javascript types then redux would be the way to go
    @jordangarcia 's examples and other nuclearjs material spoke more to me than some of the stuff in the redux ecosystem
    jma7889
    @jma7889
    Sounds like I need to learn more about nuclear-js before settle on one flux engine.
    Jack Chu
    @kamui

    it seems that moving forward to Babel 6 also breaks some functionality class StoreA extends Store { ... } doesn't seems to work

    I've seen the same issue upgrading to Babel 6

    Raul Matei
    @raulmatei
    Hi @kamui , that's a known issue, see #191 and also https://github.com/optimizely/nuclear-js/issues/213#issuecomment-184394930 - @jordangarcia said that there is a setting in Babel that could make it work, but I wasn't able to find it. One solution is to create a factory that creates your stores and some examples can be found here https://github.com/usirin/nuclear-module or here https://github.com/raulmatei/frux
    Dan Weaver
    @dan-weaver
    is there anything you all use / do to deal with complex async workflows. Something like redux-saga
    but with nuclearjs of course
    Dan Weaver
    @dan-weaver
    anyone know whats going on with #210
    kinda breaks the fundamental expectations of nuclear-js no?
    Shaun LeBron
    @shaunlebron
    Has anyone found themselves doing this, to avoid the nested dispatch error?
    setImmediate(() => someActionThatWillDispatch(...))
    I think we're caught between representing action types as both "Events" and "Store Updates"
    This is fine if a store can handle an "Event" that requires no logic, but sometimes it requires us to trigger another action, which means we must somehow execute it without doing nested dispatches
    Shaun LeBron
    @shaunlebron
    Let me make this concrete
    An Account Store listens to three action types, BOOTSTRAP, VERIFY_COMPLETE, and RESET
    the account object of the store is set by watching these action types
    David Fox-Powell
    @dtothefp
    @shaunlebron maybe changing options you instantiate the reactor with will help
    Shaun LeBron
    @shaunlebron
    interesting
    I'm wondering why nested dispatches are off by default
    like if there are some risks to be aware of I mean
    David Fox-Powell
    @dtothefp
    @shaunlebron maybe this is useful
    optimizely/nuclear-js#141
    Dan Weaver
    @dan-weaver
    hey I'm looking for some clarification... I'm not seeing ANY cacheing of my getter values
    when I mount a component no matter what, all getters get evaluated
    this is not expected right?
    all of them return immutable datastructures
    on 1.3.0
    Dan Weaver
    @dan-weaver
    nuclear react addons 0.2.0
    Dan Weaver
    @dan-weaver
    should the component not just get the cahced values rather than re evaluating?
    Dan Weaver
    @dan-weaver
    so this was related to #210 .. downgraded to 1.1.1 and it's working as I expect..
    Paulus Schoutsen
    @balloob
    What’s the future of Nuclear-JS. It seems that all discussion and maintenance have stopped after Feb 11?
    CC @jordangarcia
    Raul Matei
    @raulmatei
    @balloob @jordangarcia I have the same feeling that the development has stopped - should we start looking at the mainstream alternatives?
    Umut Sirin
    @usirin
    Everybody probably switched to redux :/
    Jackson Sandland
    @jackson-sandland
    I'm switching to NuclearJS from redux. Are there any great tutorials out there beyond the one's on the github page?
    I've been through those already, and the docs.