Martin Klepsch
Martin Klepsch
That sounds about right, yes!
I don't think I'll have time/incentives to work on this in the near future unfortunately.
I guess properly reading the README could have saved me that surprise: > This library can be used to validate and/or conform a nested associative collection (map or vector) via...
Nice, that makes sense now that I have it in front of me :)
Huh, I found something that works: ``` clj (def string-keys "Returns validation spec to ensure key is a string." (v/validator (fn [k _] (string? (last k))) "must be a string...
Thanks for the quick reply! I see why key validation probably does not make as much sense and probably will revise my model to not need key validation. I'll try...
I was thinking about something along those lines as well. It makes specs a bit harder to read and introduces another "magic" keyword though. I wonder if `:*` should then...
Your example in #5 made me think about another situation: ``` clj (v/validate {:x [nil :b :c]} {:x {:* [(v/required) (keyword-or-nil)]}}) ``` Because the wildcard is used here the `required`...
> this should only break existing validation maps in user code, but not the validators themselves... That's what I meant. :smile:
@micha do you have any thoughts on this? A solution to this probably belongs more into Boot itself than into `boot-cljsjs`.