-
-
Notifications
You must be signed in to change notification settings - Fork 616
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 info-verbosity into json schema #249
Comments
I shall take this up and subscribe to #240 PR, accordingly work on this issue. |
Nice! |
Here to help if you need anything :) |
On the other hand, looking again at the code @ev1stensberg Lines 65 to 197 in a15807b
Sorry for late reply @abiduzz420 i would like to finish my code so i will work on this issue. |
Separate configuration file is not good, would prefer it to be compact. |
In that case it should be out of outputOptions and go to options which gets validated against the schema. Any thoughts or objections? |
Send a PR, I'll review to see if its a nice thing to have in there 👍 |
Do you want to request a feature or report a bug?
Feature
What is the current behavior?
info-verbosity enum range is set within the code
If the current behavior is a bug, please provide the steps to reproduce.
What is the expected behavior?
info-verbosity enum is set in the schema, so there is no validation for it outside of validateOptions
If this is a feature request, what is motivation or use case for changing the behavior?
We are adding this option before json schema landed, but PR is there and should go in soon.
Please mention other relevant information such as the browser version, Node.js version, Operating System and programming language.
Work can be started when #240 lands into master
The text was updated successfully, but these errors were encountered: