This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-10-17
Channels
- # 100-days-of-code (5)
- # announcements (13)
- # beginners (98)
- # boot (19)
- # cider (10)
- # cljdoc (32)
- # clojure (142)
- # clojure-dev (37)
- # clojure-italy (3)
- # clojure-nl (2)
- # clojure-spec (30)
- # clojure-uk (18)
- # clojurescript (28)
- # cursive (8)
- # datomic (25)
- # duct (18)
- # editors (5)
- # emacs (39)
- # events (4)
- # figwheel (7)
- # figwheel-main (5)
- # fulcro (38)
- # graphql (19)
- # jobs-discuss (1)
- # jobs-rus (7)
- # keechma (1)
- # lumo (47)
- # off-topic (28)
- # om-next (3)
- # parinfer (3)
- # re-frame (18)
- # reagent (37)
- # reitit (8)
- # shadow-cljs (101)
- # specter (7)
- # tools-deps (8)
- # vim (1)
thanks! what would be the ideal behavior for the param keys? i could look into it if you have any ideals in mind
Thanks @ikitommi. Everything looks fine though. I'm sure I'm doing something stupid.. I'll keep digging
@vale the param route data keys… could you give an example what you would like to have?
i don't have anything in particular in mind. you said that you feel it's still wrong in your comment though, which is why i was wondering if you have any image of what would be ideal. i'd happily implement it if you had
i suspect something like this?
(s/or :kw-map (s/map-of keyword? any?)
:ds-map (s/map-of (instance? Spec) any?)
:spec s/spec?)
@vale oh, that, I did a quick fix by setting it to any?
- data-specs can have record keys (via ds/opt
and ds/req
), same applies for Schema. Also, as the coercion is pluggable, there could be.. anything. https://github.com/metosin/reitit/commit/5046aebec8c530921d39a2f6bc721c1940d6c5bd