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

IntelliSense not suggesting namespaces after using for top-level statements #58470

Open
Youssef1313 opened this issue Dec 23, 2021 · 2 comments
Assignees
Milestone

Comments

@Youssef1313
Copy link
Member

Youssef1313 commented Dec 23, 2021

Version Used:

17.1.0 P1.1

Steps to Reproduce:

  1. Trigger completion here, it works as expected.

    using System;
    using Sys$$

    image

  2. Trigger completion here, it doesn't work.

    using System;
    using Sys$$
    
    Console.WriteLine();

    image

Note that using $$ triggers IntelliSense properly. But using Sys$$ fails.

It's most likely caused by using Sys gets parsed as LocalDeclarationStatement, while using alone is parsed as an incomplete UsingDirective

@dotnet-issue-labeler dotnet-issue-labeler bot added Area-IDE untriaged Issues and PRs which have not yet been triaged by a lead labels Dec 23, 2021
@Youssef1313
Copy link
Member Author

@jinujoseph jinujoseph added Bug New Language Feature - Simple Programs Top-level statements and removed untriaged Issues and PRs which have not yet been triaged by a lead labels Jan 4, 2022
@jinujoseph jinujoseph added this to the 17.2 milestone Jan 4, 2022
@jinujoseph jinujoseph modified the milestones: 17.2, 17.3 May 5, 2022
@dfkeenan
Copy link

I was experiencing this yesterday. Seemed like if I typed anywhere other then the end of the file code completion broke down.

I was using 17.2.X.

@arkalyanms arkalyanms modified the milestones: 17.3, 17.6 P2 Jan 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants