Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Adam Stankiewicz
    @sheerun
    Coffee compilation errors are hard to read
    maybe no sourcemaps
    Christian Alfoni
    @christianalfoni
    Sweet, thanks for all the feedback. Got it noted here, so will check it out as soon as I get a chance :)
    Adam Stankiewicz
    @sheerun
    coffee is hard to debug
    Christian Alfoni
    @christianalfoni
    Hm, it should send the compilation error message from the server, which should be "okay" to read. But yeah, this is not very well tested
    Adam Stankiewicz
    @sheerun
    tab is working terribly
    especially shift+tab
    and especially in js file
    there's no vim mode
    Adam Stankiewicz
    @sheerun
    it's really easy to exit page when scrolling horizontally on touchpad
    because of chrome gestures
    It would be best to disable it somehow
    Christian Alfoni
    @christianalfoni
    Ah, that is a good point. I believe it is possible to do it. Think I did something similar some time ago
    Adam Stankiewicz
    @sheerun
    Also, I don't see document created by me
    I can only access them by saving somewhere url
    I'd also like to see history of fiddles I saw in past (not necessarily mine)
    Christian Alfoni
    @christianalfoni
    Haha, this is great stuff @sheerun, thanks. Putting them on my list :)
    Adam Stankiewicz
    @sheerun
    I also get mp3 loading errors when editing fiddle
    There is no mp3
    Christian Alfoni
    @christianalfoni
    Yeah, that is because it tries to load a recording. There is not property on the fiddle itself stating if there has been a recording... well, thinking of it, there actually is. I should check that before trying to load the mp3 :)
    Adam Stankiewicz
    @sheerun
    "Add libs" could show most popular libraries
    Before typing anything
    As a default
    Adam Stankiewicz
    @sheerun
    I think .coffee file should be untouched
    And .js file should be available
    With source maps
    Christian Alfoni
    @christianalfoni
    Doing a JSFridge bug raid this weekend, I will look into this stuff. Thanks for the reports :)
    Adam Stankiewicz
    @sheerun
    @christianalfoni I think I found view layer for flux-angular :)
    Christian Alfoni
    @christianalfoni
    Wow, that looks really interesting! Have to check it out :-) Thanks for the tip!
    Romain Sylvian
    @MyBoon
    Hey guys! I want to contribute to flux-angular by doing this : christianalfoni/flux-angular#39. Is it something we want to add?
    Christian Alfoni
    @christianalfoni
    :+1:
    Alexander
    @leitasat

    Hello everybody! I am getting warning:

    There are still stores not injected: LoginStore. Make sure to manually inject all stores before running any dispatches or set autoInjectStores to true.

    Why do I need to do that?
    Thanks

    Jason Rust
    @jrust
    Hi @leitasat, you need to do that because otherwise a flux dispatch could be dropped. The dispatch is a pub/sub model and if not all the subscribers are listening when a publish event is dispatched it would mean that the publish event may not be picked up by a store that is interested in it (in your case, the LoginStore).
    Ghost
    @ghost~54cac78adb8155e6700f3e5a

    Hello! I use webpack and to speedup build, i have following loaders for javascript:

    test: /\.js$/,
    loader: 'babel',
    include: path.resolve('src')

    obvious this is doesn't work with require('flux-angular')

    Not sure if you using common way of publishing packages on npm.

    Jason Rust
    @jrust
    That sounds like #60 -- still haven't figured out what I'm doing wrong. If you have any ideas let me know.
    Alexander
    @leitasat
    @jrust but what if all the actions which a store is subscribed to are emitted from the same part of application which injects the store? (e.g. login form in my case). So no harm can be done by a non-listening-yet store.
    Jason Rust
    @jrust
    @leitasat -- agreed that there are times when you know that your app does not have this problem, but it seemed like the developer-friendly thing to do to warn about it because it's one of those issues that could be a real pain to debug. One option would be a flag to disable the warning, the other is to just inject all stores in your app's run block
    Felix Ivan Romero Rodríguez
    @firomero
    how can i pass an object to store in flux-angular?
    Jason Rust
    @jrust
    @firomero -- not sure what you mean. You create a store using the angular.store method which will hold your state
    Felix Ivan Romero Rodríguez
    @firomero
    i would like to initialize my store with data from external source
    how can i export a set
    Jason Rust
    @jrust
    To intialize data from an async source, you could do that in your controller: e.g. $http.get('/items').then(function(response) { flux.dispatch('SET_ITEMS', response.items); })
    Felix Ivan Romero Rodríguez
    @firomero
    i was thinking do it inside the store, but now i realize is bad responsability pattern, that way is better, thanks for the advice
    Felix Ivan Romero Rodríguez
    @firomero
    bu how I ca access the items, can i do something like var items = this.state.get('items'); items = response.items. i am wondering if there are a set example
    inside the store
    Jason Rust
    @jrust
    You would do it as a handler on the store. e.g. handlers: { SET_ITEMS: 'setItems' }, setItems: function(payload) { this.state.set('items', payload); }
    Felix Ivan Romero Rodríguez
    @firomero
    thanks!!! that what I was looking for
    Jason Rust
    @jrust
    great!
    Punita Ojha
    @punitaojha
    This message was deleted