- more error info (path) in validatorRuleError
- better ubication of a rule when displaying errors (rules[3].rules[1]) like ajv when validating json schemas
- Examples
- Provide some folder examples:
- examples/basic
- examples/recursive-directories
- examples/multimatching-rules
- Provide some folder examples:
- allow rules to be exclusive
- common dir rules can have other common rules inside
- common rules can be optional
- option to print the directory structure printed
- ability to abstract common rules so we can make them shareable
- test the public api
- it should throw if no config file found
- license
- implement semantic release
- parse names starting/ending with "/" to regexp
- should have a config file .directoryvalidator.json that should work like any config file
- add a init option to create a config template
- allow RegExp in names/extensions
- create bin file
- what if you want 2 dirs in a directory and the rest can be whatever?
- { name: * } should validate all the files/dirs recursively
- better errors in console
- rename it to directory-validator
- read config from passed file
- allow dir rules to be inclusive
- commander
- program.run should accept an array of empty dirs
- right now if you pass no mainRules, it doesnt throw but if you dont pass rules to a subdirectory, it throws, what to do in this case? I think it should not throw