This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-09-04
Channels
- # announcements (5)
- # aws (12)
- # beginners (76)
- # boot (29)
- # cider (24)
- # circleci (9)
- # clojure (64)
- # clojure-dev (27)
- # clojure-europe (3)
- # clojure-houston (1)
- # clojure-italy (33)
- # clojure-nl (19)
- # clojure-poland (1)
- # clojure-spec (6)
- # clojure-uk (20)
- # clojurescript (103)
- # clojutre (1)
- # code-reviews (60)
- # cursive (76)
- # data-science (20)
- # datomic (20)
- # duct (58)
- # figwheel-main (4)
- # fulcro (36)
- # graphql (6)
- # kaocha (4)
- # onyx (1)
- # pathom (15)
- # quil (3)
- # re-frame (15)
- # reagent (15)
- # reitit (9)
- # remote-jobs (2)
- # rewrite-clj (16)
- # ring-swagger (7)
- # shadow-cljs (132)
- # spacemacs (12)
- # sql (5)
- # vim (9)
- # xtdb (12)
- # yada (4)
OK, so I don’t know if they are better or worse in terms of content, but the audio is at least non-corrupt (I hope). I was able to do new videos in a single take with minimal background noise. I also recorded a third one I’m uploading now. The videos available are now: - Getting started : minimal project setup, shadow-cljs, and a few IntelliJ tips - Normalization : A tour of how Fulcro normalizes data (both the format, and the internal mechanisms) - Initial State and Mutations: How we get the initial “frame” of data into the database for application startup, and the basics of how mutations are encoded and used.
sorry, you’re going to have to point out what you think I’m supposed to be looking for..dumping more that 2 lines of data generally is not something I have time to sift through
Oh, right sorry about that. It's that fs/dirty-fields
returns dirty fields as I expect (and use to send as diff for back-end :)) but fs/dirty?
doesn't say the form is dirty..
@U09MR0T5Y it could be a bug, it would be very helpful if you could come up with a minimal example in a gist
this is still pretty noisy IMO
thank you i appreciate that
i’m currently adding a feature to fs/dirty-fields
if there is a bug i can add it to my pull request
here are the specs for dirty fields
something minimal and easy to read like that will go a long way
I thought that fs/dirty?
and fs/dirty-fields
operate on plain data, but it seems it uses meta or walks the state-map form-state because my snippet example seems to not (entirely) reproduce the problem.
@U09FEH8GN I think this demonstrates it. Does this miss required steps?
@U09MR0T5Y where is add-config
?
Thanks @U09MR0T5Y
For the moment you could define your own dirty? function in terms of whether dirty-fields is empty or not
ah i see the bug is when a subform entity is added or removed, fs/dirty?
incorrectly reports false
i’ve added a failing test and am working on a fix
@U0CKQ19AQ i’m wondering why we don’t define fs/dirty?
in terms of fs/dirty-fields
?
there’s a small performance overhead but that’s the only downside i can think of
ok i did exactly that, otherwise i would have had to duplicate some of the core recursive logic in fs/dirty-fields
it’s in the the PR
IMO this should probably be back ported to fulcro 2
FYI we were doing something similar ourselves in our UCV project
@U09MR0T5Y thanks again for the small reproducible snippet, that always motivates us to fix things quickly 🙂
yw, really loving fulcro, things are coming together nicely lately and in big part thanks to fulcro.
that’s good to hear!
3.0.0-beta-14
has the fix
Is there a place with the API docs for Fulcro 3 (like this one https://cljdoc.org/d/fulcrologic/fulcro/2.8.13/doc/readme).