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

Cohosted Code Actions Part 1: Make code action resolve work on a document #11082

Merged
merged 30 commits into from
Oct 25, 2024

Conversation

davidwengier
Copy link
Contributor

@davidwengier davidwengier commented Oct 24, 2024

Part of #10742

The more I keep plugging away at cohosting code actions, the more I realise the PR is going to be way too big, so this is the first little bit I've pulled out from it.

It's mostly mechanical, just pulling document up to the Razor resolve context, from the individual contexts, changing the endpoint, and then fixing all the plumbing.

(New PR, from the same commit, from a feature branch so I can keep working)

@davidwengier davidwengier requested a review from a team as a code owner October 24, 2024 03:09
@davidwengier davidwengier changed the title Cohosted Code ACtions Part 1: Make code action resolve work on a document Cohosted Code Actions Part 1: Make code action resolve work on a document Oct 24, 2024
Copy link
Member

@DustinCampbell DustinCampbell left a comment

Choose a reason for hiding this comment

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

There's lots to like here. Thanks!

Part of #10742

This is the final step before actually doing something cohosting
related: Move things to the Workspaces layer and extract services from
the endpoints.

Definitely more work to do on the services to make them usable for
cohosting, but those diffs will at least be easier to view in isolation.

Commit-at-a-time is presumably a much better experience since so many
files moved, and namespaces changed, which I isolated to separate
commits.
…1083)

Part of #10742

The next round of changes is to introduce the right abstractions so that
the bulk of the code actions code can be moved to the Workspaces layer
successfully.

At least I think I got it all :D

Reviewing commit at a time probably makes sense, but up to you.
@davidwengier davidwengier merged commit 93d2032 into main Oct 25, 2024
12 checks passed
@davidwengier davidwengier deleted the dev/dawengie/CodeActionsPartOne branch October 25, 2024 01:23
@dotnet-policy-service dotnet-policy-service bot added this to the Next milestone Oct 25, 2024
@phil-allen-msft phil-allen-msft modified the milestones: Next, 17.13 P1 Oct 31, 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.

3 participants