This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-09-01
Channels
- # aws (7)
- # bangalore-clj (10)
- # beginners (27)
- # braveandtrue (4)
- # calva (2)
- # cider (9)
- # cljs-dev (20)
- # clojure (228)
- # clojure-germany (5)
- # clojure-spec (7)
- # clojurescript (32)
- # datomic (11)
- # figwheel-main (10)
- # fulcro (21)
- # hyperfiddle (3)
- # off-topic (53)
- # onyx (1)
- # portkey (2)
- # re-frame (21)
- # reagent (1)
- # shadow-cljs (5)
- # spacemacs (7)
- # specter (4)
has anyone done anything with strictly validating some data against a spec? by this i mean not allowing anything other than what’s specified. e.g. extra map keys, etc.
@spieden Several libraries have facilities for that and it's fairly easy to do. It's just not necessarily a good thing to do.
@spieden one example of such strict map validation would be s/map-of. if it specifies keywords-to-strings map - you can't have string key in there But, as Sean pointed out, it is kinda trivial to implement yourself with a particular shade of behavior you are looking for.
I've a repro for a bug where ClojureScript's spec instrument
fn generates too large a function for the JVM and compilation fails. This happens when too many fns are spec'd. https://github.com/jeaye/instrument-too-many
Looking for some confirmation.
It appears specific to ClojureScript. When I tried a similar thing in Clojure/JVM, there was no problem I noticed.
@andy.fingerhut Thanks. I've also tried it on Clojure JVM and I couldn't reproduce.