Skip to content

More CodeAction moves in preparation for cohosting#11135

Merged
davidwengier merged 6 commits intodotnet:mainfrom
davidwengier:dev/dawengie/CodeActionsPart4
Nov 1, 2024
Merged

More CodeAction moves in preparation for cohosting#11135
davidwengier merged 6 commits intodotnet:mainfrom
davidwengier:dev/dawengie/CodeActionsPart4

Conversation

@davidwengier
Copy link
Member

Okay, I was wrong when I said the last PR was the final piece before cohosting actually gets implemented, but this one is, I swear!

Code actions have to run in devenv for Roslyn, so the main thing here is re-architecting so that the endpoints call the delegated servers, because calling into the service. Each commit is an isolated step on the way.

Cohosting needs to get code actions in devenv, and will use the service in OOP
No need for cohosting to have to import a service for one method (in devenv)
As before, cohosting will need to do this in devenv
@davidwengier davidwengier requested a review from a team as a code owner November 1, 2024 05:58
@davidwengier davidwengier merged commit 70abe71 into dotnet:main Nov 1, 2024
@davidwengier davidwengier deleted the dev/dawengie/CodeActionsPart4 branch November 1, 2024 21:51
@davidwengier
Copy link
Member Author

Thank you both

@dotnet-policy-service dotnet-policy-service bot added this to the Next milestone Nov 1, 2024
davidwengier added a commit that referenced this pull request Nov 4, 2024
My bad. In #11135 I failed to notice
that the `GenerateRazorCodeActionContextAsync` also modified the
original code actions request, to handle an oddity of VS LSP, where it
sends the users selected range (or cursor position) as a different
property, and uses the `Range` property as the whole line.
@jjonescz jjonescz modified the milestones: Next, 17.13 P2 Nov 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants