This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-11-10
Channels
- # aleph (4)
- # aws (2)
- # bangalore-clj (2)
- # beginners (84)
- # boot (25)
- # cider (3)
- # cljsrn (3)
- # clojure (57)
- # clojure-italy (5)
- # clojure-losangeles (3)
- # clojure-russia (7)
- # clojure-spec (18)
- # clojure-uk (29)
- # clojurescript (90)
- # cursive (11)
- # data-science (68)
- # datascript (2)
- # datomic (25)
- # duct (3)
- # fulcro (13)
- # graphql (7)
- # immutant (1)
- # jobs (1)
- # leiningen (12)
- # lumo (1)
- # off-topic (51)
- # om (43)
- # onyx (15)
- # parinfer (10)
- # pedestal (4)
- # re-frame (7)
- # reagent (42)
- # ring-swagger (42)
- # rum (1)
- # shadow-cljs (172)
- # spacemacs (10)
- # specter (4)
- # sql (4)
- # test-check (19)
- # unrepl (54)
- # yada (3)
@currentoor I will be making a examle project with fulcro and shadow-cljs so stay tuned, I'll ping you once I am done
please let us all know 🙂
Where does PostgreSQLDatabaseManager
come from here?
https://github.com/fulcrologic/fulcro-sql
it was originally PostgreSQL only, and I generalized it but forgot to update the docs. If you want to use it with Fulcro, just use map->DatabaseManager
with a component-using :config
what is the reason behind defmutation
not supporting the ability to specify the follow-on reads - is there some benefit to only specifying them in individual om/transact!
s instead?
I was trying to find, there was a recent discussion around it
I coudn't find, but @tony.kay was talking about allowing that on Fulcro 2.0