This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-07-11
Channels
- # announcements (1)
- # aws (3)
- # beginners (48)
- # calva (2)
- # cider (47)
- # clj-kondo (1)
- # cljs-dev (23)
- # cljsrn (10)
- # clojure (81)
- # clojure-chicago (4)
- # clojure-europe (3)
- # clojure-greece (4)
- # clojure-italy (8)
- # clojure-losangeles (1)
- # clojure-nl (6)
- # clojure-sanfrancisco (1)
- # clojure-seattle (1)
- # clojure-uk (21)
- # clojurescript (40)
- # core-async (82)
- # cursive (18)
- # datomic (6)
- # duct (11)
- # figwheel-main (4)
- # fulcro (26)
- # jobs-discuss (22)
- # leiningen (18)
- # off-topic (10)
- # pathom (3)
- # re-frame (5)
- # reagent (16)
- # reitit (4)
- # shadow-cljs (8)
- # specter (7)
- # sql (16)
- # tools-deps (58)
- # xtdb (30)
Fulcro 3 book now describes the new router (mostly): http://book.fulcrologic.com/fulcro3/#_dynamic_router
http://book.fulcrologic.com/fulcro3/#_live_router_example
(defsc Main [this props]
{:ident (fn [] [:component/id ::main])
:query [:main]
:initial-state {:main "stuff"}
:route-segment ["main"]
:will-enter (fn [app route-params]
(log/info "Will enter main" route-params)
(dr/route-immediate [:component/id ::settings ;;<<<<
should be ::home
?there is also a very simple running example that will be expanded at the end of that chapter.
there could be inaccuracies in the text, but the working demo is authoritative (as far as it is written)
Can I propose to move com/fulcrologic/fulcro/dom.clj
to com/fulcrologic/fulcro/dom-macros.clj
and com/fulcrologic/fulcro/dom-server.clj
to com/fulcrologic/fulcro/dom.clj
With this, will be easier to develop cljc dom files.
I don’t feel like analyzing that problem…I spent a ton of time making that work…if you want to do that, and test it in all scenarios, and prove the macros work when possible, etc, etc, then I’m open
the problem is it is really easy to fool yourself that you got it right, when in fact you’re no longer using the macros.
oh yeah i remember wrapping my head around that macro mess…
not easy
@tony.kay Thanks for the tips on the tempid merge yesterday, it was very useful to have the :local/root installation with shadow-cljs. The issue was that I wasn't properly encoding the tempid from the server. I added the handlers but didn't properly test them. Seems to work well now! Thanks, I like the improvements fulcro 3 has added.
@tony.kay where do I find the source for the fulcro lein-template? confused a bit about the fulcro3 or legacy stuff. which one is the current?
I changed something related to deps.edn
in shadow-cljs and now you need to add thheller/shadow-cljs
manually to deps.edn
instead of the auto-inject
@thheller https://github.com/fulcro-legacy/fulcro-lein-template I’m not at the moment planning on moving that forward. Fulcro 3 has a template in progress that could be lein-en-ized I guess, but 3 is still alpha
the auto-inject was becoming a problem when importing deps.edn
projects into Cursive and so on
ah, thanks for the tip @thheller. Should we drop a direct dep on clojurescript (should we depend on the transitive dep from shadow?)