This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-04-01
Channels
- # announcements (21)
- # architecture (6)
- # aws (18)
- # babashka (14)
- # beginners (231)
- # boot (1)
- # calva (2)
- # chlorine-clover (22)
- # cider (34)
- # clara (16)
- # clj-kondo (53)
- # cljdoc (5)
- # cljs-dev (22)
- # cljsrn (3)
- # clojure (283)
- # clojure-europe (24)
- # clojure-italy (9)
- # clojure-nl (5)
- # clojure-spec (5)
- # clojure-uk (57)
- # clojurescript (14)
- # core-typed (8)
- # cursive (4)
- # data-science (11)
- # datomic (41)
- # docker (24)
- # duct (2)
- # emacs (2)
- # exercism (29)
- # fulcro (96)
- # graalvm (4)
- # jobs-discuss (1)
- # kaocha (53)
- # lambdaisland (20)
- # malli (5)
- # nrepl (4)
- # observability (7)
- # off-topic (40)
- # pathom (44)
- # pedestal (8)
- # re-frame (19)
- # shadow-cljs (58)
- # spacemacs (2)
- # sql (9)
- # tools-deps (15)
- # vim (3)
- # yada (10)
Hey Clara team I'm trying to require clara and I'm getting an error
namespace 'clara.rules.schema' not found
Any idea what I'm missing? (I am able to require 'http://calra.ruOk seems like I had a conflicting [prismatic/schema "1.1.6"] version in my classpath all good 🙂
I wonder if it would make sense to rip that dependency out of clara. I know it adds a bit of clarity to the underlying structure of the Sessions and whatnot, but it is another dependency we are forcing on consumers. @mikerod do you have any thoughts here?
Spec would probably be the ideal, but i’m not sure what all is going to have to change to uplift clojure/clojurescript versios
spec could probably be added without much difficulty on the versioning front, but actually making the spec would be more time consuming
Perhaps we can just get the schema to be an option dependency we only check/bring in during the :dev
profile?
probably isn’t easy if using harder macro features like schema’s defn
or defrecord