This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-10-06
Channels
- # beginners (32)
- # boot (17)
- # cider (4)
- # clara (112)
- # cljs-dev (3)
- # cljsjs (2)
- # clojure (222)
- # clojure-germany (3)
- # clojure-greece (1)
- # clojure-italy (4)
- # clojure-losangeles (4)
- # clojure-russia (46)
- # clojure-spec (24)
- # clojure-uk (71)
- # clojurescript (78)
- # community-development (5)
- # component (88)
- # cursive (6)
- # datomic (7)
- # duct (5)
- # figwheel (2)
- # fulcro (21)
- # graphql (22)
- # leiningen (3)
- # luminus (9)
- # off-topic (1)
- # om (16)
- # onyx (46)
- # portkey (30)
- # re-frame (47)
- # reagent (5)
- # remote-jobs (1)
- # ring (12)
- # ring-swagger (13)
- # rum (1)
- # shadow-cljs (81)
- # spacemacs (1)
- # specter (33)
- # sql (2)
- # test-check (2)
- # vim (16)
- # yada (11)
what’s the best practice for combining routes from multiple namespaces in a ring app using compojure?
for example if you had a lists and items namespace with a route.clj using the defroutes macro
is there a common pattern for bringing all those routes together in your app’s core.clj or perhaps a top level route.clj?
@chadhs that's what we do - not sure if that's best practice or not: https://github.com/WormBase/datomic-to-catalyst/blob/develop/src/rest_api/main.clj
@mgrbyte so you’re essentially just storing all the routes (defined via defroutees) from each namespace in a vector called all-routes
yes?