This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-01-04
Channels
- # aleph (1)
- # asami (6)
- # babashka (44)
- # beginners (20)
- # calva (6)
- # circleci (1)
- # clj-kondo (2)
- # cljdoc (2)
- # clojure (184)
- # clojure-europe (13)
- # clojure-nl (4)
- # clojure-spain (1)
- # clojure-uk (4)
- # clojurescript (35)
- # code-reviews (1)
- # conjure (3)
- # core-async (60)
- # core-logic (1)
- # cursive (11)
- # data-science (2)
- # events (11)
- # graalvm (4)
- # graphql (2)
- # introduce-yourself (1)
- # jobs (2)
- # leiningen (3)
- # malli (16)
- # minecraft (6)
- # practicalli (1)
- # reagent (3)
- # reitit (1)
- # releases (3)
- # remote-jobs (2)
- # rewrite-clj (21)
- # shadow-cljs (12)
- # tools-deps (21)
- # vim (16)
Is the map syntax the recommended way to go? https://github.com/metosin/malli#map-syntax
vector-syntax is the way to go, but map should work too. > NOTE: Map Syntax / SchemaAST is considered as alpha and subject to change.

and the m/=>
version there doesn’t work because if you load the whole file you load the schema, which triggers wrapping the function, and then load the function which will be unwrapped
Plumatic style. Cant wait to see it released ;3
I think we can solve the dev-tooöing issues with first two, with polling and var-watching.
any progress on the timing problem with metadata? https://clojurians.slack.com/archives/C03S1KBA2/p1628602192164200
seems tricky to deal with the case where a var is defined and then immediately used