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 completions after unsafe in using directive #68334

Merged
merged 5 commits into from
Jun 6, 2023

Conversation

DoctorKrolic
Copy link
Contributor

Fixes: #67985

@DoctorKrolic DoctorKrolic requested a review from a team as a code owner May 26, 2023 09:20
@dotnet-issue-labeler dotnet-issue-labeler bot added Area-IDE untriaged Issues and PRs which have not yet been triaged by a lead labels May 26, 2023
@ghost ghost added the Community The pull request was submitted by a contributor who is not a Microsoft employee. label May 26, 2023
yield return new[] { "abstract" };
yield return new[] { "class" };
yield return new[] { "delegate" };
yield return new[] { "file" };
Copy link
Member

Choose a reason for hiding this comment

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

file would be fine. it's just a normal identifier.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

In this context file comes from a keyword recommender and therefore has keyword glyph. I think, this makes it more confusing than helpful. Also leaving file here would introduce a major inconsistency since neither file nor any other contextual keyword is shown in name context, where it can be treated as identifier

Copy link
Member

Choose a reason for hiding this comment

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

wfm.

note: i would far prefer these tests be in their respective provider test files. In other words, we should test 'class' in the tests for 'class'.

@DoctorKrolic
Copy link
Contributor Author

@CyrusNajmabadi PTAL/merge

@CyrusNajmabadi
Copy link
Member

looking

@CyrusNajmabadi
Copy link
Member

Thanks!

@CyrusNajmabadi CyrusNajmabadi merged commit 826e177 into dotnet:main Jun 6, 2023
@ghost ghost added this to the Next milestone Jun 6, 2023
@DoctorKrolic DoctorKrolic deleted the using-unsafe-completions branch June 6, 2023 19:14
@RikkiGibson RikkiGibson modified the milestones: Next, 17.7 P3 Jun 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-IDE Community The pull request was submitted by a contributor who is not a Microsoft employee. untriaged Issues and PRs which have not yet been triaged by a lead
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Unexpected recommendations after unsafe keyword in using declarations
3 participants