This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-06-05
Channels
- # announcements (11)
- # architecture (22)
- # babashka (33)
- # beginners (15)
- # biff (8)
- # calva (7)
- # clj-otel (1)
- # cljs-dev (3)
- # cljsrn (5)
- # clojure (76)
- # clojure-art (1)
- # clojure-europe (36)
- # clojure-hamburg (3)
- # clojure-nl (1)
- # clojure-norway (7)
- # clojure-poland (12)
- # clojure-spec (2)
- # clojure-uk (7)
- # clojurescript (9)
- # cursive (22)
- # data-science (6)
- # datomic (7)
- # fulcro (9)
- # hoplon (14)
- # instaparse (2)
- # jobs-discuss (14)
- # london-clojurians (1)
- # matrix (32)
- # music (1)
- # nbb (8)
- # off-topic (18)
- # pathom (29)
- # pedestal (6)
- # portal (34)
- # reagent (2)
- # reitit (4)
- # releases (1)
- # sci (10)
- # shadow-cljs (7)
- # tools-deps (4)
- # vim (6)
The main change to watch out for is related to path parameters in routing: https://github.com/pedestal/pedestal/issues/588
It seems to say, that if a program uses path parameters then it won't work anymore? That's a big breaking change. Is there guidance for a workaround?
It's actually the opposite; an existing program will have set up its own logic to decode path parameters, but now that (by default) happens automatically and you may decode path parameters twice, which is wasteful and occasionally will cause errors (for instance, if a %
is encoded as %37
it will decode once to %
then fail when decoding the second time (either erroring, or consuming two hex digits that follow it).