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

Blazor : razor editor does not suggest any intellisense options, until I enter a character and then delete it, then it works fine #10749

Open
vsfeedback opened this issue Aug 15, 2024 · 1 comment
Assignees
Labels
area-compiler Umbrella for all compiler issues author: migration bot 🤖 The issue was created by a issue mover bot. The author may not be the actual author untriaged
Milestone

Comments

@vsfeedback
Copy link

This issue has been moved from a ticket on Developer Community.


[severity:It's more difficult to complete my work]
As descried above, please see recording. What you'll see is that I'll do the following:

  1. add an attribute to a razor compononet, I would expect that intellisense pops up offering me suggestions
  2. nothing happens, I'll try CTRL + SPACE, CTRL + . etc
  3. if I type any character and delete it, then CTRL + SPACE automatically populates it with the correct starting type

Why is this? it would save me a lot of time if this worked without having to type the character and delete it.


Original Comments

Feedback Bot on 7/31/2024, 06:50 PM:

(private comment, text removed)

Phil Allen [MSFT] on 8/1/2024, 02:53 PM:

(private comment, text removed)

Lee Ramsingh on 8/2/2024, 07:32 AM:

(private comment, text removed)

Lee Ramsingh on 8/5/2024, 10:19 AM:

(private comment, text removed)

Feedback Bot on 8/15/2024, 02:49 PM:

(private comment, text removed)


Original Solutions

(no solutions)

@dotnet-policy-service dotnet-policy-service bot added untriaged author: migration bot 🤖 The issue was created by a issue mover bot. The author may not be the actual author labels Aug 15, 2024
@chsienki
Copy link
Contributor

So, I think this is actually very similar to the case I'm fixing with @inject in fuse. The issue occurs because there isn't any C# yet to actually provide IntelliSense on. When you start typing, we emit enough info to get the IntelliSense, and going back a character keeps you in the same IntelliSense session(? Don't know what it's called) so the completion dialog stays up.

We're fixing this for @inject by essentially emitting an 'error' style token, which is valid C#. In that case its ok because there is also an RZ diagnostic that prevents compilation. I think that might be the case here too, so we might be able to fix it in the same way.

@chsienki chsienki self-assigned this Aug 22, 2024
@chsienki chsienki added the area-compiler Umbrella for all compiler issues label Aug 22, 2024
@chsienki chsienki added this to the Backlog milestone Aug 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-compiler Umbrella for all compiler issues author: migration bot 🤖 The issue was created by a issue mover bot. The author may not be the actual author untriaged
Projects
None yet
Development

No branches or pull requests

2 participants