@jaerme From looking at the project.clj, I don’t think the source paths are correct for the example builds. The examples haven’t been touched in 2 years so I’m sure they are from Om.now. If you want to compile them anyway you might try changing the :source-paths for the “hello” build to “src/main” instead of “src” here: https://github.com/omcljs/om/blob/master/project.clj#L56

What does :pathopt mean in Om Next?

@peeja means "path optimization"

it’s useful to start computing queries from a certain sub-tree when doing incremental rendering

instead of at the root

this example uses path optimization: https://github.com/omcljs/om/blob/master/src/devcards/om/devcards/core.cljs#L311-L397

Ah, neat. That makes more sense than "path optional". 🙂

Does anyone know of examples besides in the om wiki where set-query! / update-query! are used?

https://github.com/omcljs/om/pull/764

💪

@dnolen ^ had a little time to kill

@anmonteiro haha 🙂

@anmonteiro how was the conf?

@dnolen good good! lots of awesome talks, and got the opportunity to chat with Jafar Husain

@anmonteiro oh cool nice! Was he doing another Falcor thing?

nah, he was there giving a talk about new JS features

@dnolen btw was a bummer that I had to miss ClojuTRE. looking forward to the video of your talk

@anmonteiro it went over well and I got to tell some stories some people weren’t familiar with

now I have to think about what to say at EuroClojure 🙂

I have been struggling with myself not to ask what that talk is going to be about 🙂

since it says “TBD"

heh well your guess is as good as mine at this point 😛

ah, now I get the “TBD”

haha

really excited for EuroClojure

that one I’ll definitely be there!

so am I, it should be a lot of fun

@dnolen btw and also related to my question earlier in #cljs-dev. My server-side rendering PR breaks support for bootstrap CLJS because of :require-macros in the om.next namespace

any ideas on how to solve that one?

thinking that we’ll need a macros NS at this point

I’ll have to think about that

but then I’m not sure how to have defui be in the om.next namespace

it’s OK since server side rendering is a tad higher priority that bootstrap support

another solution would be not to require-macros in om.next and have users write :refer-macros

which would mean they can’t :refer [defui] (with current implicit macro loading support)

yeah

I understand the problem

gotcha