Skip to content

Workaround for #15972 #15982

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

Merged
merged 3 commits into from
Sep 16, 2023
Merged

Conversation

vzarytovskii
Copy link
Member

@vzarytovskii vzarytovskii commented Sep 15, 2023

After talking to @0101, we decided to make a workaround for #15972 by not excluding parsing/syntax errors from semantic ones, just in case if proper fix doesn't make it to P3.

Worst case scenario, parsing errors will be doubled.

It shows errors right now:

image_2023-09-15_15-23-26

@vzarytovskii vzarytovskii requested a review from a team as a code owner September 15, 2023 13:28
@vzarytovskii
Copy link
Member Author

Alright, some of the diagnostics tests are expectedly failing, I will either fix them or disable (since we'll likely revert the change once roslyn has a fix).

…ail once we rollback the change, but forget to rollback tests
@vzarytovskii
Copy link
Member Author

Ok, not proud of the fix, but it will fail if we rollback the workaround but forget tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

3 participants