This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-02-15
Channels
- # announcements (5)
- # babashka (56)
- # beginners (24)
- # biff (15)
- # calva (7)
- # clj-kondo (12)
- # cljsrn (8)
- # clojure (68)
- # clojure-denmark (1)
- # clojure-europe (55)
- # clojure-norway (4)
- # clojure-spec (9)
- # clojure-uk (2)
- # clojurescript (8)
- # cursive (11)
- # data-science (7)
- # datahike (1)
- # datomic (66)
- # emacs (12)
- # etaoin (3)
- # fulcro (10)
- # graphql (3)
- # hyperfiddle (97)
- # jobs (1)
- # kaocha (8)
- # lsp (3)
- # malli (15)
- # meander (1)
- # off-topic (3)
- # overtone (4)
- # polylith (7)
- # rdf (25)
- # re-frame (4)
- # reagent (14)
- # remote-jobs (1)
- # shadow-cljs (126)
- # sql (30)
- # vscode (3)
- # xtdb (8)
Is there any guidance out there on organizing larger lacinia projects, particularly in terms of splitting up schema and resolver files? Do people prefer to keep a single large schema file and/or single large resolvers file? And if not, along what lines do they split things up?
At Walmart, we were federated, so we made use of a single SDL file and our architecture involved very few resolvers, primarily just the root operations. Certainly, I vastly prefered the inject-resolvers approach to the attach-resolvers approach (the latter dating back to the non-public Lacinia prototype, before I even joined Walmart).
Interesting, I was wondering about switching to an SDL file from EDN!