Skip to content
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

fix: error logged via a console.error doesn't show as red in debug console #173366

Merged
merged 1 commit into from Feb 3, 2023

Conversation

connor4312
Copy link
Member

With the changes earlier this week, severity now works for expression elements, but it wasn't being set.

Fixes #171732

…nsole

With the changes earlier this week, severity now works for expression elements, but it wasn't being set.

Fixes #171732
@connor4312 connor4312 self-assigned this Feb 3, 2023
@VSCodeTriageBot VSCodeTriageBot added this to the February 2023 milestone Feb 3, 2023
@connor4312 connor4312 merged commit 9992acd into main Feb 3, 2023
@connor4312 connor4312 deleted the connor4312/issue171732 branch February 3, 2023 21:28
c-claeys pushed a commit to c-claeys/vscode that referenced this pull request Feb 16, 2023
…nsole (microsoft#173366)

With the changes earlier this week, severity now works for expression elements, but it wasn't being set.

Fixes microsoft#171732
@github-actions github-actions bot locked and limited conversation to collaborators Mar 20, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Angular error logged via a console.log doesn't show as red in debug console
3 participants