This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-10-13
Channels
- # beginners (67)
- # boot (18)
- # cider (28)
- # clara (11)
- # cljs-dev (1)
- # cljsrn (7)
- # clojure (134)
- # clojure-dev (2)
- # clojure-dusseldorf (1)
- # clojure-greece (1)
- # clojure-italy (13)
- # clojure-losangeles (2)
- # clojure-nl (2)
- # clojure-russia (2)
- # clojure-spec (2)
- # clojure-uk (52)
- # clojurebridge-ams (1)
- # clojurescript (78)
- # core-async (1)
- # core-matrix (2)
- # cursive (12)
- # data-science (22)
- # emacs (10)
- # events (1)
- # fulcro (28)
- # graphql (4)
- # hoplon (16)
- # jobs (1)
- # lein-figwheel (3)
- # leiningen (3)
- # nyc (1)
- # off-topic (19)
- # onyx (70)
- # parinfer (2)
- # pedestal (1)
- # portkey (9)
- # protorepl (2)
- # re-frame (16)
- # reagent (39)
- # ring-swagger (5)
- # rum (1)
- # schema (2)
- # shadow-cljs (216)
- # specter (5)
- # sql (1)
- # uncomplicate (4)
- # unrepl (6)
- # vim (25)
- # yada (5)
thanks heaps. clear - let me assimilate this..
I see this error in my console when trying to call set-state:
No queries exist for component path (atlas-crm.fulcro.router/Root atlas-crm.fulcro.router/TopRouter atlas-crm.fulcro.router/TopRouter-Union atlas-crm.sales.views/SalesView atlas-crm.sales.components.sale-funnel/Funnel atlas-crm.sales.components.sale-funnel/FunnelStage)
This path seems correct and exists. So not sure what causes this. I a trying to interface with react-dnd so maybe they are screwing something up@mitchelkuijpers This error is thrown when Om tries to figure out the focused query from root for a given refresh. What’s weird is I had always assumed component-local state did not run a query for refresh. But I’m looking at the code now, and it sorta looks like it does. That seems like not much of an optimization if it is true.
actually if it is stateless, then it just uses React…it is only if it is stateful (has a query) that it does more
Does the component, or one above it, unmount/mount during your problematic sequence?
It is a component that uses state for changing orders. For performance reasons
I saw on om some related unreleased changes
Will test out further tomorrow
And we are not using path opt
We fixed it for now by using react-set-state btw
cool, but that still means there is a possible problem should you do a transact there, since it will run the same code sequence
Yeah not a problem for now, but I ran into this problem two or three times before. Can never figure out the issue. I do give a function to another component somewhere that calls set-state
It matters that set-state gets called by a component (e.g. the this
) that is on-screen and will be refreshed
if the component had been unmounted during the UI change, for example, then no query would be foudn for it because it wouldn’t be indexed anymore
I thought this might be related but I might be wrong: https://github.com/omcljs/om/issues/860
@tony.kay Just tested the change out, completely fixes the problem!
@bnoguchi Is a total hero, could never figure out what I was doing wrong ^^
I think this is already merged into om? https://github.com/omcljs/om/pull/861
Yeah but there is no version released yet
Really needed the set-state, for showing a preview where something would drop on dragging stuff. om/transact is waaay to slow to do stuff like that.
Everyone: I’m very interested in hearing if any of you are using dynamic queries (`set-query!`) beyond the DynamicRouter
. The current design of Om Next’s dynamic queries is incompatible with some things I’d like to accomplish in Fulcro, but I have no desire to break existing applications that use Fulcro. So, feedback is strongly desired.