I've been debugging this for awhile and don't understand what's happening.
I am debating between these two possibilities:
(om/build-all row sequence {:opts {:edit edit}})
vs.
(om/build-all row sequence {:state {:edit edit}})
The second is the typical idiom I use but I don't think it's necessary all the
time. And in this example, this works when I reference the :state version's
"edit" inside this:
(render-state [_ {:keys [edit]}]
.... use "edit" somewhere
What I tried doing is using :opts instead. Then my "row" fn looked like this
(extra arg):
(defn row
[value owner {:keys [edit]}]
.....
(render-state [_ _] ; removed state info
.... use "edit" somewhere
Should I not expect "edit" to work as a readable value in render-state in both
cases? I am not *setting* it, hence why I don't need it as state, so :opts
seems better in this case.
But when I do the above with :opts, "edit" is nil. I don't want to use :state
just because I can't get :opts working. Is there anything obvious I am
overlooking?
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/clojurescript.
