-
Notifications
You must be signed in to change notification settings - Fork 23
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
error only spotlight option #172
Comments
Yes, It makes sense to add a |
Beyond my ability. Wish I could; we're operating just outside my wheelhouse here and I'd love to expand said wheelhouse. (Brain issues slowing me down, hopefully temporarily.) |
Arg. Please ignore that. I will return and reply more clearly and possibly even correctly. |
I won't be able to make this happen (health issues.) |
Looks like we already have Is this enough or should we introduce new flag for error only? |
for my purposes an error-only flag would be helfpul; I'd like to prevent scraping and scrapping pointless warnings in my results. as mentioned above, "almost broken" has no value in my use of the tool, only "all the way broken". |
Rather than adding new flag for showing errors only, I have added argument to filter by status, like |
matching existing code is perfect. excellent. thanks very much. |
Would like an option to spotlight only errors, and not include warnings.
For myself, warnings are essentially meaningless. "Almost broken" doesn't warrant my attention.
The text was updated successfully, but these errors were encountered: