This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-11-11
Channels
- # asami (19)
- # babashka (41)
- # beginners (115)
- # biff (7)
- # calva (78)
- # clj-kondo (29)
- # cljs-dev (9)
- # clojure (39)
- # clojure-europe (17)
- # clojure-gamedev (29)
- # clojure-nl (1)
- # clojure-norway (9)
- # clojure-spec (2)
- # clojure-uk (3)
- # clojurescript (7)
- # core-async (26)
- # cursive (16)
- # datomic (13)
- # emacs (1)
- # events (5)
- # fulcro (2)
- # funcool (4)
- # gratitude (1)
- # helix (1)
- # holy-lambda (1)
- # humbleui (1)
- # introduce-yourself (4)
- # java (1)
- # jobs (2)
- # jobs-discuss (9)
- # lsp (28)
- # matcher-combinators (2)
- # mathematics (1)
- # membrane (1)
- # nbb (12)
- # off-topic (10)
- # pathom (52)
- # polylith (38)
- # portal (32)
- # re-frame (4)
- # reagent (16)
- # reitit (2)
- # remote-jobs (1)
- # reveal (1)
- # rewrite-clj (10)
- # sci (67)
- # shadow-cljs (45)
- # squint (1)
- # tools-build (13)
- # tools-deps (16)
The next HL release will introduce some breaking changes (meaning you will have to tweak your code to run Lambdas on new runtime) and two toggles. • normalize-headers? (default: true) - headers of input event for http api & AWS api gateway will be in shape of [string, lowercased string] instead of [keyword, string]. To stay with the current behavior you will have to set it to false. • normalize-body? (default: true) - HL already automatically normalizes the body but it puts the result in :body-parsed instead of body. Starting from the next release the normalization will be optional and the result will be injected into the body instead of :body-parsed. Why? I see more people interested in trying out hl-ring-adapter and those changes will make the ring<->hl integration smoother and more performant. Sorry for the inconvenience. This time I’ve traded full backwards compatibility for the performance 😇