I do not think so.
If you check the example schema, it is very hard to understand it. What does ':lat' mean? is it a string or a number?
What does '!b' mean, can it only be false?
If you read the whole example:
lat = custom validator
b = shorthand for boolean (as is s for string)
! = optional
So for me reading the whole example its very easy to understand and digest.
Yes, reading the docs explains what these keywords mean. But by just looking at the schema it is impossible to understand what that is. And if you check the definition of clean code which is something like "intuitive understandable" then it comes clear that this is not clean.
Ah I see where you’re coming from. Good point.
The “!” for optional is the only thing that confused me. Why not “?” for optional?