This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-06-02
Channels
- # announcements (37)
- # babashka (9)
- # beginners (172)
- # calva (7)
- # cestmeetup (28)
- # chlorine-clover (27)
- # clj-kondo (2)
- # cljs-dev (45)
- # cljsrn (8)
- # clojure (185)
- # clojure-dev (27)
- # clojure-europe (6)
- # clojure-finland (3)
- # clojure-nl (5)
- # clojure-uk (13)
- # clojuredesign-podcast (4)
- # clojurescript (54)
- # conjure (19)
- # core-typed (1)
- # cursive (40)
- # datomic (9)
- # emacs (5)
- # figwheel-main (34)
- # fulcro (238)
- # graphql (14)
- # hugsql (3)
- # leiningen (4)
- # malli (6)
- # off-topic (12)
- # pedestal (5)
- # portkey (19)
- # protorepl (8)
- # rdf (2)
- # re-frame (23)
- # reagent (3)
- # reitit (16)
- # shadow-cljs (29)
- # spacemacs (12)
- # sql (1)
- # xtdb (15)
and the event today: https://clojureverse.org/t/new-online-meetup-clojure-european-summer-time/6018/6
Just a thought: one thing that makes debugging Malli structures hard is that it doesn't retain any information of how it was composed. If you def a SubPart and then def a Part based on that using mu/union that info is lost. Not that it would always be possible (because schemas can just be created programatically) but it might be useful to stuff something into Meta to display it later in the explain.
In Minimallist, there are :let and :ref nodes which make composition of models explicit.
Maybe Malli will get something similar once it supports recursion.
there is also some thinking in the README about entities & values: https://github.com/metosin/malli#entities-and-values