This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-11-14
Channels
- # adventofcode (1)
- # babashka (60)
- # beginners (107)
- # calva (11)
- # cider (3)
- # clara (11)
- # clj-kondo (6)
- # cljs-dev (33)
- # clojure (70)
- # clojure-dev (4)
- # clojure-europe (3)
- # clojure-italy (2)
- # clojure-kc (1)
- # clojure-losangeles (12)
- # clojure-nl (4)
- # clojure-spec (32)
- # clojure-uk (35)
- # clojuredesign-podcast (1)
- # clojurescript (28)
- # core-logic (4)
- # cursive (5)
- # datomic (34)
- # devcards (1)
- # emacs (16)
- # events (13)
- # fulcro (15)
- # graalvm (5)
- # graphql (3)
- # jobs (8)
- # joker (2)
- # kaocha (17)
- # malli (6)
- # music (3)
- # off-topic (58)
- # protorepl (7)
- # re-frame (28)
- # rewrite-clj (9)
- # shadow-cljs (102)
- # spacemacs (3)
- # sql (20)
- # tools-deps (9)
I’m not sure if I like that str
is directly usable in schemas like that. From user point of view I’d assume my own namespace requires to apply, not implicit ones from within malli and in that case I’d rather see an error…I do see the usefulness of that, but it makes me go a bit :face_with_raised_eyebrow: Eh, maybe that’s just me…
you can explicitly allow certain qualified symbols to be used, could allow that via global options. I guess clojure.string
is a dependency and is available for users of malli. BUT, might fail with advanced compilation unless explixitely registered those functions. Explicit is always better…
though of exposing explicitely some clojure.test.check.generators
functions for generators, to enable portable generators with :gen/gen
schema property. Those definitions should be in optional ns so if not needed, doesn’t make the bundle size bigger.
better portable example in a tweet: https://twitter.com/ikitommi/status/1194555187995848705
@suomi.esko actually, the str
stuff is explicitly allowed in sci, so ok: https://github.com/borkdude/sci/blob/9b70708c5c42e89d94a72aa961bfa1d3a6ef8be4/src/sci/impl/namespaces.cljc#L437-L475