is it ok to om/transact! during a (defmethod mutate…)?

@arohner maybe, but it more ok just to swap!, should give you the same end result, Im pretty sure you will hit a problem in the long run doing recursive transactions.

How do you do your (dom/label #js {:htmlFor ?})

thought query should be [:me-mail] not [{:me-mail '[*]}] for a simple property?

@fenton you need to clarify what your problem is

what did you expect to see (and where) vs. what you're seeing

this works:

cljs.user=> (om/db->tree [:me-mail] @my-state @my-state)
{:me-mail ""}

Is {:value [:foo]} in a (defmethod mutate) supposed to work? Everything behaves fine when I (om/transact c [(foo) :foo]), but doesn’t work when I (om/transact c [(foo)]), with {:value [:foo]} in the defmethod

i.e. the page doesn’t re-render based on :foo changing

@arohner https://github.com/omcljs/om/wiki/Om-Next-FAQ#what-does-value-keys--do-from-a-mutation-result-map

(spoilers: it doesn't mean absolutely nothing 🙂 )

I’m really confused at what it should do then

https://github.com/omcljs/om/wiki/Documentation-(om.next)#parser

also, it seems like a nice feature to have, so the “api” around what should happen when you (transact [(foo)]) is more encapsulated

needing to specify (transact [(foo) :foo]) everywhere in your app seems like an opportunity for bugs

@arohner you can always wrap your transact! calls with your own function

so what does {:value {:keys []}} do then?

nothing

should it be removed from the docstring of om/parser then?

I don't see why

I think the docstring is consistent with the behavior

what behavior? you just said it does nothing?

:value is an optional hint at keys affected by the mutation; it has no effect on rerendering

behavior, or lack of thereof

FWIW, I’ve found the docs for om.next to be incredibly frustrating, more so than om now. I’d be happy to help improve them, but I don’t know enough about how it works yet.

yeah, they're lacking a bunch of things

Hopefully we'll be able to put together a website soon enough, with good documentation

@anmonteiro I've always been confused by that too: hint to whom? Is there a way that my own code should/could be reading the :keys value coming out of the parser and reacting to it?

@peeja yeah I think you can use the return value of transact!

for remote stuff you'll have :keys in the merge's res

I mean, I see that it's there, but is there anything useful to do with it?

Oh, that's interesting

you can queue them for re-rendering

you can call another transact! too with those keys

e.g. (transact! this [:foo :bar])

transacts don't necessarily need to have a mutation 🙂

Oh, yeah, neat

@peeja btw have you checked out the new Compassus release?

seems to have all the stuff you were asking for 🙂

@anmonteiro: Ooh lovely! Will do!

check out the changelog for breaking changes

everything's written down there, should be easy enough to upgrade

serious newbie question, but assuming I have a bunch of factory functions for my defui created components, is there an easier way to render a hierarchy them dynamically than passing invocations of the factory functions as children?

i.e. right now I have something like (component-a {:children (component-b {:children (component-c {:some-prop 123})

although what’s happening is intuitive, it feels a little unwieldy

@mss hrm normally the way I render children is:

(component-a nil
  (component-b nil
    (component-c {:some-prop 123})))

ahhh I was mistaken about the signature of the factory fn

you can get a component's children through (om.next/children this)

thanks so much for the help, really appreciate it

Ok, stupid question, that didn’t seem to be documented anywhere. if I create a component with its factory, passing nil to props, it can query from the root of the app-state?!

hrm, this seems connected to transacting. a default read behaves as I previously expected

but I have a component being called with no props that, after a transaction, reads as if it was querying the root

(defui Foo static om/IQuery [:foo/bar]) (foo) (om/transact rx [(foo/bar {:value “hello”})])