As Om's build-all takes a sequence of cursors, I'm wondering the best practice
for when the component function passed to build-all needs to lookup its item
from the sequence to get more info about it from a different cursor in the
app-state, i.e. in a relational database type of way:
(defn app-state
(atom {:attributes {... map of an id to info about that id ...}
:id-sequence [id1 id5 id4 id7... etc as if based on a sorting order
or other sequence, perhaps even repeated items]}))
Now suppose I want to call build-all on :id-sequence but then use info from
:attributes after getting an item from the vector?
One bloated option would be to create a new sequence in the app state that
holds the id and its attributes, which would mean for repeated ids the same
attributes are stored multiple times.
Unlike other Om components, I'm guessing build-all is not designed to accept
multiple cursors since it needs a single sequence to do its thing.
Can anyone advise a good approach?
--
Note that posts from new members are moderated - please be patient with your
first post.
---
You received this message because you are subscribed to the Google Groups
"ClojureScript" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at http://groups.google.com/group/clojurescript.
