This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-02-11
Channels
- # architecture (1)
- # babashka (61)
- # babashka-sci-dev (1)
- # beginners (85)
- # calva (112)
- # clj-kondo (279)
- # cljdoc (16)
- # cljs-dev (15)
- # cljsrn (7)
- # clojure (168)
- # clojure-europe (36)
- # clojure-nl (10)
- # clojure-spec (6)
- # clojure-uk (5)
- # clojured (1)
- # clojurescript (20)
- # core-async (16)
- # crypto (2)
- # cursive (13)
- # datomic (25)
- # events (7)
- # fulcro (21)
- # google-cloud (3)
- # graalvm (2)
- # graalvm-mobile (2)
- # gratitude (3)
- # helix (20)
- # honeysql (4)
- # hugsql (15)
- # introduce-yourself (15)
- # leiningen (2)
- # lsp (24)
- # luminus (22)
- # malli (21)
- # meander (11)
- # midje (1)
- # other-languages (1)
- # pathom (8)
- # re-frame (5)
- # reagent (5)
- # releases (2)
- # reveal (1)
- # shadow-cljs (18)
- # spacemacs (17)
- # sql (9)
- # tools-build (12)
- # tools-deps (4)
- # vim (12)
If I want to use fulcro RAD only for the html5 history support, should I be creating a base fulcro app, or a fulcro rad app?
Is think fulcro is good enough
IMO you should always have RAD be in your deps…use the parts of it that are convenient. Having support for quick ways to stand up support forms/reports for your own backoffice use is just super handy. It’s all just extras on top of fulcro
Yea it has some great tools in there. A lot of it isn't relevant in my case because I'm doing really custom storage stuff, specifically with git and raw files, but RAD has a lot more than just storage adapters available.
That sounds intriguing :)
The storage adapters are not at all needed to use forms/reports…that simply requires a network API that can query/save, and the save is nicely generalized.
Yea looking at the docs I think I could write my own save/delete middleware and leverage more of rad than I originally thought.
Seems the only difference is some csrf token stuff and a default remote, which I don't need
Hello again. I'm noticing lots of uism warnings of the form Attempt to get an ASM path :some/path for a state machine that is not in Fulcro state.
simply by using state machines. I've followed the instructions https://book.fulcrologic.com/#warn-uism-sm-not-in-state to no avail. I even receive these warnings without mounting my UI...is this a known thing?
> Note: As of Fulcro 3.5.6, you are likely to get the Attempt to get an ASM path… error for the router because dr/initialize! is asynchronous and does not finish before the dr/change-route! call. You can safely ignore it. https://fulcro-community.github.io/guides/tutorial-advanced-minimalist-fulcro/#_the_bare_essentials_of_fulcro_routing
Although I can make this happen even without using the dynamic router, so it seems to be something within the state machines themselves that's spewing warnings.
YW. That's come up a few times. I'm on my way out right now but I'll add a note about it in the Fulcro book next time I get around to editing it.
Seems I can create an empty state machine definition and use uism/begin!
during initialization and still receive the warnings, even with everything else commented out. Something inside the begin!
call isn't happy.
Could be the same problem as with routing that it tries to access the state before it was initialized...