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

CompletionOptions from Multiple Language Servers Aren't Respected #5497

Closed
TanayParikh opened this issue Apr 29, 2020 · 8 comments · Fixed by #1948
Closed

CompletionOptions from Multiple Language Servers Aren't Respected #5497

TanayParikh opened this issue Apr 29, 2020 · 8 comments · Fixed by #1948
Assignees
Milestone

Comments

@TanayParikh
Copy link
Contributor

If I add:

AllCommitCharacters = new[] { ":", ">" },

to the Razor.LanguageServer CompletionOptions here these characters aren't accepted to commit completions proposed by this language server.

I have to add the commit char (:) to the LanguageServerClient CompletionOptions here.

Now even though the Razor.LanguageServer proposes the completion, and doesn't have any commit characters specified in the CompletionOptions, :, which was specified in the LanguageServerClient successfully commits the completion.

This poses as issue in cases like this where we want : to commit the @onkeypress razor directive attribute but not the onkeypress html attribute.

@TanayParikh
Copy link
Contributor Author

TanayParikh commented Apr 29, 2020

Once this issue is resolved, https://github.com/dotnet/aspnetcore-tooling/pull/1825/files#diff-dddd024b99ebbf567eea61e984e7a9f6R21 needs to be updated to remove the : commit char.

AllCommitCharacters = new[] { ":", ">", " ", "=" },

also needs to be added to the Razor.LanguageServer CompletionOptions here to allow for commits of Razor directive attributes and <text> tags.

@NTaylorMullen
Copy link
Contributor

NTaylorMullen commented Apr 29, 2020

Should file a vsts issue to track this as well and make sure the LSP platform team knows about it

@TanayParikh TanayParikh self-assigned this May 5, 2020
@TanayParikh
Copy link
Contributor Author

TanayParikh commented May 5, 2020

#1825 has been merged in.

Created a VSTS issue and reached out to the appropriate team to see if we can get this resolved to support CompletionOptions.AllCommitCharacters from multiple language servers. Marking as blocked as it has an external dependency.

@TanayParikh
Copy link
Contributor Author

The fix for this was merged in and inserted. Will verify once the new build propagates.

@TanayParikh
Copy link
Contributor Author

Tried out the latest insertion, however the issue seems to persist.

Investigated into the VS LSP codebase, and identified a potential issue. Following up with them on the existing VSTS issue.

@TanayParikh
Copy link
Contributor Author

New VSTS Issue.

@TanayParikh
Copy link
Contributor Author

TanayParikh commented Jul 7, 2020

Still blocked externally by LSP Platform, backlog'ing for now. Followed up with LSP Platform and will update accordingly.

@TanayParikh
Copy link
Contributor Author

This should be unblocked soon (LSP Platform just inserted this in).

@ghost ghost locked as resolved and limited conversation to collaborators Aug 13, 2020
@ghost ghost unlocked this conversation Oct 9, 2021
@allisonchou allisonchou transferred this issue from dotnet/aspnetcore Oct 9, 2021
@allisonchou allisonchou modified the milestones: 16.7-Preview1, 16.8-Preview1 Oct 9, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Nov 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants