This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-04-28
Channels
- # asami (13)
- # babashka (6)
- # beginners (38)
- # calva (14)
- # cider (15)
- # circleci (13)
- # clj-kondo (4)
- # cljsrn (18)
- # clojure (164)
- # clojure-bay-area (3)
- # clojure-europe (46)
- # clojure-italy (8)
- # clojure-losangeles (3)
- # clojure-norway (3)
- # clojure-sweden (24)
- # clojure-uk (115)
- # clojurescript (79)
- # cursive (11)
- # datomic (24)
- # docker (2)
- # events (9)
- # figwheel-main (31)
- # fulcro (5)
- # honeysql (6)
- # jackdaw (7)
- # jobs (3)
- # jobs-discuss (16)
- # joker (1)
- # kaocha (6)
- # keechma (1)
- # lein-figwheel (1)
- # malli (6)
- # pathom (10)
- # podcasts-discuss (13)
- # practicalli (3)
- # react (4)
- # reagent (3)
- # reitit (8)
- # remote-jobs (3)
- # shadow-cljs (21)
- # sql (12)
- # tools-deps (20)
- # xtdb (24)
@tony.kay How to troubleshoot when Fulcro Inspect DB is empty even though there is data in the client DB?
When you look into the current app -> ::app/state-atom
, I see the data I expect. But Fulcro Inspect DB and DB Explorer show no data. Otherwise F.I. is working, i.e. Pick Element works just fine. This is how I set up and render the app, which I do at the end of my namespace, not inside shadow's init fn:
(app/mount! (app/fulcro-app {:initial-db
{:page/heading "<3> Fulcro is:"
:page/value-proposition-points [{:proposition/label "Malleable"}]}})
Root "app" {:initialize-state? false})
The full code is here: https://github.com/fulcro-community/fulcro-exercises/blob/tmp/inspect-db-broken/src/holyjak/fulcro_exercises.cljs#L89. PS: I have the <script ...>
that loads the .cljs code just before </body>
but that should not matter?
Any ideas where the problem could be or how to troubleshoot it? Thank you!synchronization of the db to inspect is a rather cmplicated affair, and it is not without bugs at the moment. Fulcro has the client side of inspect in its source code, and mount calls a method to tell inspect that the app is there. Sounds like that part is working if you can pick elements. The client-side keeps track of db versions during dev as a numbered history. All it sends to inspect on each transaction is what db version has just been made. Then, once those updates settle down Inspect itself sends a message back to the app and asks for the content. If you right-click on Inspect itself and “Inspect Element” you’ll get a Chrome console that is Inspect’s (hows that for circular). Look for console errors. Could be you have something in state that cannot be serialized over the comm channel, and you might see errors in that console.
Thank you! I have indeed errors there, 2 of > persistence.js:1 File system error: A requested file or directory could not be found at the time an operation was processed. when requesting entry '' and 8 of > main.js:4157 ERROR [fulcro.inspect.chrome.devtool.main:176] - Something was nil So I guess I would need to run Inspect in debug mode to find out more, right?
There are developer instructions in the inspect repo. feel free. You might also just try reinstaling the plugin. I’ve not had it act up in a way that is consistently non-functional
Announcement: https://github.com/fulcro-community/fulcro-exercises is ready for beta testers! fulcro-exercises is a follow-up to the Minimalist Fulcro Tutorial to get hands dirty with Fulcro and learn and experience the theory in practice, through a series of gradually more challenging exercises. Please give it a try and let me know about your thoughts and suggestions! 🙏