Closed john2x closed 10 years ago
That's definitely a good point. Originally, these were kept as is not to introduce breaking changes. It might be an idea to mark the current functions that modify atoms as deprecated and create new ones using the standard !
postfix.
Updating the documentation is definitely a good idea as well.
I could do the docs if you want. I've been drafting a blog post about a walkthrough with Luminus, and I just finished the part where I explain a bit about the validation namespace.
I'll definitely update the docs for now, but this is something I wanted to clean up for a little while. Right now the API is breaking the standard convention, which isn't good. :)
Cool, thanks! Should this be closed or...?
Let's wait till I make the updates so I don't forget about it. :)
ok new version of lib-noir is up, I updated the docs and released a new luminus template with the latest version
@john2x btw I added some docs in the luminus site http://www.luminusweb.net/docs/input_validation.md let me know if it all makes sense :)
Looks great :)
Maybe the docs could be improved? Mention in
wrap-noir-validation
that it adds an*errors*
binding of an atom, and it gets populated by the various functions provided by the validation namespace. Right now, unless you read the source, it's not clear where the errors are stored.And/or maybe add the
!
suffix torule
,set-error
andclear-errors
? But that would break the API.