is it possible in chrome dev tools (maybe with React Dev Tools) to see a query of a component?

you can call the query static method on any component that implement om/IQuery protocol

you could do this from repll inside DevTools using amazing Dirac repl 🙂

hrmm, I thought you could but I just tried and it's not working for me... maybe I'm doing something wrong

(def foo (new TimeLoop)) > foo ∅⊢IQuerymqueryλ[this]inom.nextjsfunction ()jsio$smitten$om$timeloop$TimeLooprefs: Objectstate: Objectupdater: Objectcontext: undefinedprops: undefined__proto__: ObjectTimeLoop > (.query foo) TypeError: io.smitten.om.timeloop.foo.query is not a function

any feedbacks on using d3 or one visualization lib with om.next ?

baptiste-from-paris: d3 works fine

baptiste-from-paris: there’s a cljsjs/d3 so you dont need to stub it out either

thx @matthavener

not a pain to write components with it and React/om ?

not really, just hook into the react lifecycle methods (componentDidXXX)

its kind “outside” the react model, but its really not much different than using react/d3 together

anything you read online for react/d3 will apply.. you’re just getting rendered by om.next driven updates

ok, thx

have you tried other libs for data viz ?

i haven't

Anybody seen issues with hot code reloading causing "No queries exist for component path (...)" errors?

I've got the indexer logging and I can plainly see the component path in the component-path->query map, and on initial render everything is fine, but when I reload code all of a sudden I start getting the No queries error in my console, even though the component-path->query map still shows it's there. My only guess was maybe somehow the code reloading causes weirdness with the component path matching?

But that doesn't really make sense because all my other queries work fine with code reloading.

what do you mean all your other queries work fine? is just one component failing?

As far as I can tell, yeah, just this one component

is a code snippet possible?

Actually, nevermind, it's multiple components - this one was just the most obvious

to be captain obvious, are you using ^:once ?

Good question.

Looks like we were not using ^:once in our defui wrapper, but that doesn't seem to help here.

I think I've seen that happen, perhaps when using dynamic queries (`set-query!` and co.)

@therabidbanana is that the case?

Nah - we don't use set-query! anywhere. I think I put the ^:once in the wrong macro though. I'll try that again.

I don't know that ^:once will help your case

might be more worthwhile to defonce the reconciler and the state, etc

so that it doesn't get wiped on reloads

seems strange though that its working elsewhere

I think it's not, it just seemed like it was because the other components weren't failing as noticeably

are you using untangled?

Yeah

so i assume you’ve already got the new-untangled-client in a defonce

Yeah. I'm pretty sure this used to at least seem like it worked better - I feel like it started throwing this specific issue after upgrading our app to alpha47.

sounds like you should start verifying that first

maybe a good ol’ fashion git bisect