This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # announcements (8)
- # asami (10)
- # babashka (16)
- # beginners (86)
- # calva (22)
- # chlorine-clover (9)
- # circleci (20)
- # clj-kondo (13)
- # cljs-dev (20)
- # cljsrn (3)
- # clojure (144)
- # clojure-australia (10)
- # clojure-europe (126)
- # clojure-italy (5)
- # clojure-nl (8)
- # clojure-norway (4)
- # clojure-serbia (9)
- # clojure-uk (7)
- # clojurescript (14)
- # cursive (20)
- # data-science (1)
- # datomic (20)
- # figwheel-main (5)
- # fulcro (23)
- # graalvm (7)
- # graphql (25)
- # honeysql (15)
- # hugsql (3)
- # jobs (2)
- # lambdaisland (2)
- # leiningen (4)
- # lsp (102)
- # malli (3)
- # off-topic (51)
- # overtone (5)
- # pathom (27)
- # portal (11)
- # quil (1)
- # re-frame (19)
- # reagent (31)
- # remote-jobs (1)
- # reveal (3)
- # rewrite-clj (56)
- # shadow-cljs (45)
- # startup-in-a-month (1)
- # tools-deps (9)
My app DB is empty in Fulcro Inspect. I’ve gone back to what I thought was a previously working version, but it’s still empty. The app is working normally. Any tips for how to troubleshoot it?
So, I’m not aware of any issues with the latest version and Chrome. If you right-click on Inspect itself and Inspect it (very meta) to open up the console on the plugin, you can clear the application data and see if that fixes it. Sometimes a bad value gets in there and hoses things. Uninstall/reinstall has the same effect.
oh nice about the meta tools, I didn’t realize that was possible. now after building with 3.4.20 I’m getting a a few errors. I’ll attempt to resolve those and circle back if I’m still having problems
it’s working now. It looks like the problem was that I introduced some strange data that triggered a strange error that wasn’t previously getting warned about, but the newer fulcro seemed to surface it. Thanks for the help!
Another pass at Fulcro in vanilla hooks-based React apps. SHA 0a52e40e49f40d6b2a0c6900ba2841c4709f2af0, and on develop. After some discussion with @wilkerlucio we decided that it might be nice to just be able to specify a query. It occurred to me that it is pretty easy to infer auto-normalization with a simple rule: the first prop with an
id for the keyword’s
name is how to look up the ident. So, even for things that have a constant ident you can just include a
:ui/id in the query and a
:ui/id :settings kv pair in the state.
The final usage looks like (example todo list):
feel free to play with it and give feedback. I deployed a snapshot as 3.4.21-SNAPSHOT if you don’t use deps.
Will give that a try next time I run into the need! Thanks. Already using the
use-query-subscription with alternate render in some spaces.
I've been having issues with my app crashing when using it on iOS, most horrible browser to debug ever 🔥, Taking the crown from IE6, ironic considering the initial stance of Apple towards html5 apps.
I figured it's probably mostly caused by scrolling a list that's "too big", although it's only 10-20 items with maybe 10 dom elements and some strings as children, nothing crazy..
react-window but it seems since it wraps a class this messes with the fulcro bindings.
I think this applies for solving it, but that sounds like something I want to avoid. Any tips?
great, react-virtuoso seems much better so far, seems to work with
comp/with-parent-context plus it reads dynamic item without needing to calculate it manually.
I have modified the Fulcro React Native demo. I have a Session component which works fine with the Login interaction and the state machine. I have been able to get the user id inside the Session component. I need to use this in other components in my UI, e.g., to get addresses etc. for the current user. I don't know how to acccess the user id from outside the Session component. Any suggestions would be greatly appreciated...
Use an ident join in a query. For example, if you loaded it at the top level using
:current-user, then the state has
:current-user [:session/id some-user-id] (or something similar). You can just add
[:current-user '_] to any component’s query, and it will resolve it.
What is the point of defining initial state? Is it in cases where initial state differs from the queried state? Couldn't we just use the queries and pass in server-side data?
@marcus.akre this is a common misunderstanding. Fulcro is a reified data view. Initial state is what data needs to be populated into the UI before any loads have ever happened. Without initial state, what do the UI queries have to query? The component queries are usable by loads, but are always used to get data from the local db.