Closed timwis closed 8 years ago
Yeah, I think this is better handled by validation. You can take a look at the next
branch to get a sneak peek. I'm basically allowing for all of validator.js in the config, so you should be able to have pretty fine-grained control.
Alright, take a look now. Tons of validation options :)
Nice! Sounds like a productive weekend :) I guess I'd use the length.min
validator
This may be a total bad idea, but when I use
.env
files, I provide a.env.sample
with empty env vars, ie:And my readme tells folks to copy the file to
.env
and fill them in. If they copy/rename it but don't fill them in, they won't get a warning. I can see how this might contradict a circumstance when you intentionally want a var blank.Maybe this fits into your validation ideas? ie. "not allowed to be empty"