-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
OutputEvent objects should respect output severity #16420
Comments
@roblourens looking at the code we do not use severity in a case for OutputEvent with a variablesReference. It is simply ignored. For me to investigate further I would need exact repro steps |
Sorry, I must have changed two things at once, because the actual problem I'm having is with this check |
But the fact that severity is ignored is also an issue, right? Opened a new issue for the |
I was hoping to use variablesReference for all output events, not just ones that contain objects, for consistency. If it's better to check the types that were logged and fall back on the original behavior for strings, I can do that. But I think it would be good if there could be an indicator that an object was logged as an error, or thrown. It should stand out if you're skimming the log. |
@roblourens but what would happen if you log an object as an error. Only the top level object would get decorated as an error or all children would also get decorated as an error. |
This seems really important to me. If you have an app producing lots of logs, exceptions and errors need to stand out. For node/chrome, I expect to use it for any |
Ok, let me assign back to me since you think it is important. |
@isidorn Are you still planning on this for the month? Let me know if I can help. |
@roblourens yeah I actually planed to look into it tomorrow. You can help me by letting me know how would you expect this to behave. Is it fine if only the top level object is colored red and then all the children as usual? That would fix your concern of making it easier to spot in a lot of output |
Cool, yeah what you describe is just how I'd expect it to behave. I may take a look, thanks. |
If category is stderr, then 'variables' is never called.
The text was updated successfully, but these errors were encountered: