Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add config validation #44

Closed
ifedchankau opened this issue Jul 19, 2018 · 1 comment
Closed

Add config validation #44

ifedchankau opened this issue Jul 19, 2018 · 1 comment
Assignees

Comments

@ifedchankau
Copy link
Collaborator

Please, add validation of configuration, which should have:

  • validation of config correctness
  • empty values filling with defaults
ifedchankau added a commit to ifedchankau/usage-parser that referenced this issue Jul 20, 2018
Added:
- default config (template/defaultConfig.json)
- schema of config (template/configSchema.json)
- function configValidation, that is validating config with schema and filling it with defaults (if empty)

Closes linterhub#44
ifedchankau added a commit to ifedchankau/usage-parser that referenced this issue Jul 20, 2018
Added:
- default config (template/defaultConfig.json)
- schema of config (template/configSchema.json)
- function configValidation, that is validating config with schema and filling it with defaults (if empty)

Closes linterhub#44
ifedchankau added a commit to ifedchankau/usage-parser that referenced this issue Jul 20, 2018
Added:
- default config (template/defaultConfig.json)
- schema of config (template/configSchema.json)
- function configValidation, that is validating config with schema and filling it with defaults (if empty)

Closes linterhub#44
itekaf pushed a commit that referenced this issue Jul 20, 2018
Added:
- default config (template/defaultConfig.json)
- schema of config (template/configSchema.json)
- function configValidation, that is validating config with schema and filling it with defaults (if empty)

Closes #44
@itekaf
Copy link
Contributor

itekaf commented Aug 20, 2018

🎉 This issue has been resolved in version 1.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants