This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-02-12
Channels
- # aleph (22)
- # aws (7)
- # babashka (17)
- # beginners (69)
- # chlorine-clover (9)
- # cider (2)
- # clj-kondo (3)
- # cljdoc (30)
- # clojure (113)
- # clojure-dev (30)
- # clojure-europe (11)
- # clojure-italy (2)
- # clojure-nl (16)
- # clojure-spec (1)
- # clojure-sweden (3)
- # clojure-uk (17)
- # clojurescript (77)
- # cryogen (12)
- # data-science (5)
- # datomic (27)
- # duct (2)
- # emacs (37)
- # fulcro (24)
- # graphql (2)
- # kaocha (1)
- # lambdaisland (27)
- # leiningen (4)
- # off-topic (15)
- # onyx (1)
- # other-lisps (3)
- # re-frame (94)
- # reagent (2)
- # reitit (20)
- # ring (1)
- # shadow-cljs (66)
- # spacemacs (5)
- # sql (59)
- # tools-deps (140)
- # vim (1)
- # xtdb (17)
If a form has subforms and one is added creating a tempid entry in a root table and also in the parent’s subforms link list, and then the whole session is cancelled, pristine->entity* only removes the link from the parent’s list, but the item still remains in the root table. Is there an existing helper for getting rid of all the temp subform items from their root tables on cancel?
Cleaning up stuff like that isn’t really an issue from any performance or memory perspective usually, but there are helpers in notmalized-state: https://cljdoc.org/d/com.fulcrologic/fulcro/3.1.8/api/com.fulcrologic.fulcro.algorithms.normalized-state#remove-entity
@tony.kay Fulcro and fulcro-rad is very awesome. Will there be a fulcro-rad-crux library?
If someone writes it 😉 The adapters are quite small…The Datomic adapter, for example, is about 550 LOC at the moment, and won’t be getting much larger than that, and it supports sharding, auto-generated resolvers, connection mocking, and some testing utils. Most of the important stuff is done in layers above.
thanks.😀
if you use the datomic adapter
i believe someone is writing a sql adapter, i would assume CRUD is supported
crud is one of the core features of rad after all
yes looks like it does
fulcrologic / fulcro-rad-datomic > The current version only supports on-prem with a PostgreSQL store. There is nothing in the design that requires this, it has just not yet been generalized. Is this still the case? Meaning no Datomic Cloud support yet?
most likely meaning has not been tested with anything other than on-prem
i’d suggest reading through the source it’s only a couple hundred lines of code
see if there are any calls to d/entity
(not supported in the client lib)
and i believe there are some other API differences but i don’t remember all of them
however despite all that i think it would be pretty straightforward to adapt this code to the client lib, i.e. cloud compatible
no problem