This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-11-13
Channels
- # aleph (1)
- # announcements (18)
- # babashka (11)
- # beginners (112)
- # business (1)
- # calva (19)
- # cider (8)
- # clj-kondo (63)
- # cljsrn (10)
- # clojure (188)
- # clojure-australia (1)
- # clojure-dev (38)
- # clojure-europe (112)
- # clojure-nl (3)
- # clojure-provo (1)
- # clojure-spec (22)
- # clojure-uk (108)
- # clojurescript (37)
- # cryogen (4)
- # cursive (8)
- # data-science (1)
- # datomic (13)
- # emacs (9)
- # events (1)
- # fulcro (26)
- # funcool (3)
- # graalvm (2)
- # graphql (11)
- # helix (8)
- # jobs (1)
- # jobs-discuss (7)
- # nrepl (3)
- # off-topic (72)
- # pathom (10)
- # pedestal (1)
- # reagent (6)
- # reitit (7)
- # remote-jobs (1)
- # shadow-cljs (28)
- # xtdb (12)
Hi, all. What’s the right way to transform route data prior to passing it to reitit-ring/router
? Say I want to add some additional [:swagger :tags]
based on my own keys I’ve added at points in the tree. I looked at adding an :expand
fn, but data
coming in there is pre-meta-merge.
Just reading up on composing routers. So would it be something like this?
(-> route-defs ring/router ring/routes transform-routes ring/router)
@frankleonrose yes, there could be a new callback fn for this.
Thanks! If I understand correctly, second pass on conflict resolution should result in no change (assuming my transform doesn’t change paths).