-
Notifications
You must be signed in to change notification settings - Fork 0
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 check for keywords does not violate with pre-defined keys on 'dever init' #27
Comments
czprz
added a commit
that referenced
this issue
Jan 31, 2022
…eywords conflict with pre-defined keys
czprz
added a commit
that referenced
this issue
Feb 6, 2022
czprz
added a commit
that referenced
this issue
Feb 6, 2022
+ Removed console message when project cannot be found. As this should not be part of the config handler
czprz
added a commit
that referenced
this issue
Feb 6, 2022
+ Added new simple implementation of dever.json validate command + Created constant helper to have a central location for predefined keys
czprz
added a commit
that referenced
this issue
Feb 6, 2022
czprz
added a commit
that referenced
this issue
Feb 6, 2022
czprz
added a commit
that referenced
this issue
Feb 6, 2022
czprz
added a commit
that referenced
this issue
Feb 6, 2022
#27 Ensure project keywords does not conflict with pre-defined keys
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Check that 'init', 'list' and 'config' is not a keyword within projects found by 'dever init'. As these keys cannot be used.
Add logic in 'dever init' to not include dever.json which violates pre-defined keys.
Add 'validate' option to only check keywords
The text was updated successfully, but these errors were encountered: