This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-02-13
Channels
- # adventofcode (35)
- # announcements (2)
- # arachne (1)
- # beginners (71)
- # chestnut (2)
- # cider (100)
- # cljdoc (17)
- # cljs-dev (17)
- # cljsjs (2)
- # cljsrn (2)
- # clojure (53)
- # clojure-austin (2)
- # clojure-europe (1)
- # clojure-finland (2)
- # clojure-italy (3)
- # clojure-nl (7)
- # clojure-russia (56)
- # clojure-spec (56)
- # clojure-uk (35)
- # clojurescript (58)
- # community-development (14)
- # core-async (9)
- # cursive (22)
- # data-science (5)
- # datomic (14)
- # duct (5)
- # emacs (2)
- # expound (4)
- # figwheel-main (6)
- # fulcro (23)
- # kaocha (8)
- # lumo (7)
- # off-topic (10)
- # pathom (6)
- # re-frame (17)
- # reitit (31)
- # ring (3)
- # rum (1)
- # shadow-cljs (45)
- # spacemacs (10)
- # sql (12)
- # testing (9)
- # tools-deps (130)
@currentoor yeah its inside a router
then same, make up a router
the component thing worked, but I guess I’m confused why I have to make it up @currentoor
@njj so we have a normalized app state, and the way to reach entities in this structure (with queries) is with an ident, which give an entity a unique and specific identity
routers use both idents and queries for that purpose
Hi im using form-state and found something that i’m questioning if its intended behavior. If I have a field which is an unrequired subform
, my form-delta shows {:before nil :after []}
when calling form-state/dirty-fields
for this field without changing anything.
I might have found an issue is the function form-state/dirty-fields
.
https://github.com/fulcrologic/fulcro/blob/develop/src/main/fulcro/ui/form_state.cljc#L479
If items
is nil
, cond
will succeed for the :else
case, making a vector the current-value instead of nil
If I specify :initial-state
through new-fulcro-client
can I also specify initial state in components? From a quick experiment, it looks like the component's initial state fn is called but the resulting value is not merged into the db coming from new-fulcro-client
.
@mark340 if you specify :initial-state
, the initial state coming from components isn’t used
(however you could manually pull in the initial state coming from components and merge it in)
I don't think so, the content looks different and that repo hasn't been updated since april 2018 while the link i posted was updatd in December
I build/deploy that to a separate server…eventually maybe I’ll set it up to deploy to the github-based website.
Fulcro Incubator 0.0.28 is up on Clojars. This version adds a few tweaks to the dynamic router and better support for load/remoting within UI state machines. https://github.com/fulcrologic/fulcro-incubator
I think that fixed the problem I was running into. I got it working before by setting the :deferred-timeout really high, but now it works even if it's low
FYI this is what I have currently working: https://gist.github.com/thosmos/93ee78b2d508630b13e31cc9e858bdde
I’m curious what the benefit of the dom macros have over Sablono?
http://tonsky.me/blog/hiccup/ nice article about this stuff.
Thanks that was super helpful. I had those assumptions but wasn’t 100% sure that my assumptions were correct