Fork me on GitHub
#om
<
2015-12-25
>
sander00:12:44

@mudphone: i also noticed that things updated sometimes, maybe only the child that called transact! will automatically have an updated read by default or something

sander00:12:11

anyway the docs are quite clear on what to expect: "The query expression should contain any keys which should be re-read following the mutations (e.g. :todos/list). These reads will schedule components which depend on the specified keys to re-render."

mudphone00:12:47

@sander: ah, excellent… I need to throughly read the docs… I’ve been looking at the wikis.

noonian00:12:44

I believe the component that calls transact will implicitly have its query appended to the transaction as a read. I could be wrong as not very much in om next is implicit.

dnolen00:12:07

@noonian: you’re right that’s one of the few implicit things

mudphone00:12:32

the docs for transact! really clear it up for me, like @sander said

not-much-io15:12:49

Doing Tony Kays nice om tutorial -https://github.com/awkay/om-tutorial I wonder if someone here has solved them and has the solutions available? I am kinda stuck..

sllyq18:12:16

I have done B and C if you need help with those simple_smile

not-much-io18:12:26

@sllyq: C exercise 3 solution would be grand to have simple_smile

sllyq18:12:40

have you checked om_tutorial/app_database/solutions.cljs?

not-much-io18:12:31

haha, had no idea that was there 😅 thnx a bunch, will use that simple_smile

steveb8n21:12:53

Thanks @dnolen I can work around it for now

steveb8n21:12:06

Best of the season to everyone. This is such a great group to be a part of :)