-
Notifications
You must be signed in to change notification settings - Fork 8
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
Option to ignore errors from stderr instead of erroring out #17
Comments
I actually like the idea of making it entirely userconfigurable instead of hardcoded so I've implemented it. Should be in the next release :) |
I can't get over how fast you are! I'm very grateful for your work :) |
Just an idea: maybe it could support substrings so one could just specify For example, this
becomes this:
since there's only a find and replace happening. I believe this can be updated right here (9a53527#diff-cb9065f770e90db317f3d505d67589dc098bab45986df0aaaa32d2f192cc558eR185) to ignore the entire error instead of just removing a bit of it. Not sure if the current implementation bases the output on lines, but that would probably be necessary given this case, or you could jerryrig regex to work per line instead. All of this is assuming this is the path you want to take here - I don't want to impose, this just something I thought would be beneficial for myself and other users of this extension. |
Thanks for the suggestion. After thinking about it I've gone for something that is pretty close to this namely regexes. That way you can just do |
Great call, just allowing regular expressions really gives as much (or as little) power as anyone could want. |
I saw #16 and figured that maybe a configuration setting where you can specify an array of "ignore strings" that a user can supply themselves so that way it's not hard coding something like 'XDebug' or 'Warning:'. I'm running into a similar situation because my execution environment is different than my development environment.
If you're open to the idea but don't want to work on it, I can give it a go.
The text was updated successfully, but these errors were encountered: