4 ms·

Don't cursors still suffer from the problem of intermediate components needing to pass on state they don't use? For example, a list of articles might have an au

Don't cursors still suffer from the problem of intermediate components needing to pass on state they don't use? For example, a list of articles might have an author for each article. Then you have the following components: App > ArticleList > ArticleItem. So App will have to have a list of authors and a list of articles, and pass that down to ArticleList, which, for each Article, will instantiate an ArticleItem and also find the correct author to pass to it. Instead, what if ArticleItem just got an Article, and then asked the author store to give it the Author? ArticleList shouldn't really care about the authors. The example is a bit contrived, but hopefully you see the problem? Especially consider if there are a couple more layers between App and whatever leaf component is rendering something,

dustingetz 12y ago
I use cursors in JavaScript with a flux architecture, and yes, prop passing is a problem for us. I've rationalized it as "there are more wires, but the wires are straight and bundled, not a ratsnest of spaghetti references" https://github.com/wingspan/wingspan-cursor/blob/master/js/Cursor.js https://github.com/wingspan/wingspan-cursor/blob/master/js/C...
skybrian 12y ago
How about passing a createArticleTag() function to ArticleList, so that access to the AuthorStore gets passed down via the closure rather than explicitly?
arobbins 12y ago
In Om, components can still look at the global state without using a cursor if they want. You could have a top level "authors" key in the data store that the ArticleItems would have hardcoded into them. They could look up the author themselves as you describe by looking up the "authors" key in the global data state. Alternately, you can pass multiple cursors[1] to a component. In your example, you could pass each ArticleItem a cursor pointing to the right article, and a more general cursor pointing to the author store. This would eliminate the hard coding of "authors", but it would require ArticleList to pass along some sort of "additional-data" cursor. [1] https://github.com/swannodette/om/wiki/Cursors#using-multiple-cursors https://github.com/swannodette/om/wiki/Cursors#using-multipl...

dustingetz 12y ago

I use cursors in JavaScript with a flux architecture, and yes, prop passing is a problem for us. I've rationalized it as "there are more wires, but the wires are straight and bundled, not a ratsnest of spaghetti references" https://github.com/wingspan/wingspan-cursor/blob/master/js/Cursor.js https://github.com/wingspan/wingspan-cursor/blob/master/js/C...

skybrian 12y ago

How about passing a createArticleTag() function to ArticleList, so that access to the AuthorStore gets passed down via the closure rather than explicitly?

arobbins 12y ago

In Om, components can still look at the global state without using a cursor if they want. You could have a top level "authors" key in the data store that the ArticleItems would have hardcoded into them. They could look up the author themselves as you describe by looking up the "authors" key in the global data state. Alternately, you can pass multiple cursors[1] to a component. In your example, you could pass each ArticleItem a cursor pointing to the right article, and a more general cursor pointing to the author store. This would eliminate the hard coding of "authors", but it would require ArticleList to pass along some sort of "additional-data" cursor. [1] https://github.com/swannodette/om/wiki/Cursors#using-multiple-cursors https://github.com/swannodette/om/wiki/Cursors#using-multipl...