-
Notifications
You must be signed in to change notification settings - Fork 3
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
Enum patterns #142
Comments
ifedchankau
added a commit
to ifedchankau/usage-parser
that referenced
this issue
Aug 15, 2018
- Add more enum patterns - Delete unnecessary values (path, file, etc.) from parsing as enum Closes linterhub#142
ifedchankau
added a commit
to ifedchankau/usage-parser
that referenced
this issue
Aug 15, 2018
- Add more enum patterns - Delete unnecessary values (path, file, etc.) from parsing as enum Closes linterhub#142
ifedchankau
added a commit
to ifedchankau/usage-parser
that referenced
this issue
Aug 15, 2018
- Add more enum patterns - Delete unnecessary values (path, file, etc.) from parsing as enum Closes linterhub#142
ifedchankau
added a commit
to ifedchankau/usage-parser
that referenced
this issue
Aug 15, 2018
- Add more enum patterns - Delete unnecessary values (path, file, etc.) from parsing as enum Closes linterhub#142
ifedchankau
added a commit
to ifedchankau/usage-parser
that referenced
this issue
Aug 15, 2018
- Add more enum patterns - Delete unnecessary values (path, file, etc.) from parsing as enum Closes linterhub#142
🎉 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
I've found next enum patterns in different documentations:
(auto|always|never, default to never)
Custom reporter (<PATH>|jslint|checkstyle|unix)
Options: "scss", "sass", "less", "sugarss"
formatter: "json", "string" or "verbose"
Please, add this patterns.
Also, i've found, that
<file|folder>
now parsing as enum. Please, fix it.The text was updated successfully, but these errors were encountered: