In some life-cycle methods you need to deref and others you don't. I found it
confusing until I got that straight.
On May 29, 2015, at 1:11 PM, John Chijioke wrote:
> I also didn't understand that was what David meant by "you absolutely need to
> deref".
>
> --
> Note that posts from new me
I also didn't understand that was what David meant by "you absolutely need to
deref".
--
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 unsubscrib
Thanks a lot for that pointer. I really appreciate.
--
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
: *clojurescript@googlegroups.com
>
> *Reply To: *clojurescript@googlegroups.com
>
> *Subject: *Re: [ClojureScript] In Om, why does transact not update cursor
> value.
>
> om/value is the cached value that was seen at the start of render which is
> useful to know. You need
Hi David,Then the name should be more like om/cached-value or om/init-value. It's very misleading as om/value. And I suggest there should be a name for getting the current value as having to do (get-in @(om/state
om/value is the cached value that was seen at the start of render which is
useful to know. You need to deref if you absolutely need to see what the
current value is.
David
On Mon, May 25, 2015 at 1:05 PM, John Chijioke wrote:
> When a transact has happened to cursor successfully. Why does (om/v
When a transact has happened to cursor successfully. Why does (om/value cursor)
not return the current value in (om/state cursor) at (om/path cursor)?
John.
--
Note that posts from new members are moderated - please be patient with your
first post.
---
You received this message because you ar
