Feature request: Validation of UNIX file path about strictyaml HOT 7 CLOSED

Please make sure the PR comes accompanied with a story that verifies and describes the change though. E.g. modify this story: https://github.com/crdoconnor/strictyaml/blob/master/hitch/email-url.story

Thanks!

from strictyaml.

FYI i realized earlier that I hadn't been very clear about how to set up a development environment. If that's useful, I've written up instructions here: https://hitchdev.com/approach/contributing-to-hitch-libraries/

Anything that's not clear, doesn't work, etc. let me know. I haven't had many contributors before, so I'd like to smooth the process out. Thanks!

from strictyaml.

Ok cool. I'm closing this for now, but feel free to reopen if you have any new ideas or find anything else of interest.

from strictyaml.

Yep, I'd love that.

from strictyaml.

UNIX file path validation seems to be a bit tricky in practice. StrictYaml should probably only do plain syntax validation I guess. Means I wouldn't consider OS and filesystem specifics. Only / and NUL seem to be invalid UNIX file path characters (/ is name-separator character). However a regex like [^\0]+ (one or more characters not NUL) could raise a lot of false positives.

from strictyaml.

Interesting. I'm actually not even sure if a NUL character will parse in YAML (it probably shouldn't).

Either way, the fact that damn near everything is apparently a valid file path suggests that just using Str is probably the best approach.

from strictyaml.

I agree. I'll stick to Str syntax validation for now.

from strictyaml.