Many thanks John.
I'll check out phrase. If you do get something working I'd love to see it
as your approach seems the simplest to me.
cheers
Dave
On Monday, February 3, 2020 at 10:27:08 PM UTC, John Shaffer wrote:
>
> The phrase library can create human-readable error messages:
> https://gith
You're misunderstanding me. I'll try again.
I'm not saying you can't navigate to keys that don't exist in the data --
but since there would be no corresponding value, the nav call would be (nav
coll k nil) essentially.
If (get coll k) produces some value v, then (nav coll k v) will take you
from
Hi.
Wanted to update that I decided not to be involved in GSoC 2020.
Another option, similar and different, that some of us are discussing
elsewhere is Rails Girls SoC 2020.
https://railsgirlssummerofcode.org
https://railsgirlssummerofcode.org/about/
I like the idea that it actively seeks divers
The phrase library can create human-readable error messages:
https://github.com/alexanderkiel/phrase
I've been working on something for a more natural (to me) approach, with
the ability to define error messages in-line with the predicate. E.g.,
(s/defop max-length [n]
(sf/validator
#(>= n (
Hi All.
I've just come back to Clojure (after being away for a few years) and I'm
incredibly impressed with how things have moved on. I particuarly like
Clojure Spec but I'm struggling to understand how I can convert coercion
erros to a human friendly for for end users to understand on a websit
This is what I've done but it contradicts what we said earlier...
If I navigate to some existing key and it gives me back a Java object, then
it means that the datafied representation had a key pointing to non data!
I have read your blog post multiple times ;), but I think the situation
you're de
