Skip to content

Don't report unused diagnostics when the unused node has a parse error - #25598

Merged
2 commits merged into
masterfrom
noSuggestionDiagnosticsOnParseError
Jul 13, 2018
Merged

Don't report unused diagnostics when the unused node has a parse error#25598
2 commits merged into
masterfrom
noSuggestionDiagnosticsOnParseError

Conversation

@ghost

Copy link
Copy Markdown

Fixes#25591

@ghost
ghost force-pushed the noSuggestionDiagnosticsOnParseError branch from 23d0bae to e26e448CompareJuly 12, 2018 01:56

@amcaseyAndrew Casey (amcasey) left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems reasonable, assuming Matt confirms it doesn't cause flicker.

@ghostghost changed the title Don't report suggestion diagnostics when a parse error existsDon't report unused diagnostics when the unused node has a parse errorJul 12, 2018
@ghost

Copy link
Copy Markdown
Author

Waiting for Matt Bierner (@mjbvz) to verify

@mjbvz

Copy link
Copy Markdown

Andy (Andrewkraft) (@Andy-MS) I'm still see the diagnostics when using the TS version from this PR, at least for the cases in #25591

@ghost

Copy link
Copy Markdown
Author

Here's what it looks like to me:

typescript@next:
next

jake local on the noSuggestionDiagnosticsOnParseError branch:
branch

@mjbvz

Copy link
Copy Markdown

Andy (Andrewkraft) (@Andy-MS) You're right. I ran the wrong build command. Seems to be working well. I haven't notice any flickering or other odd behavior in my testing

@ghost
ghost merged commit 1fb050b into masterJul 13, 2018
@ghost
ghost deleted the noSuggestionDiagnosticsOnParseError branch July 13, 2018 00:25
@microsoftMicrosoft (microsoft) locked as resolved and limited conversation to collaborators Oct 21, 2025
This pull request was closed.
Sign up for freeto 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.

3 participants

@mjbvz@mhegazy@amcasey