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

Expose folding range functionality to Razor #73609

Merged
merged 4 commits into from
May 21, 2024

Conversation

davidwengier
Copy link
Contributor

Three things:

  • Allow Razor to get folding ranges through a C# call rather than LSP
  • Expose LSP types through restricted IVT so we don't have to wrap the return from the above call
  • Minor fix to Json formatter code just in case

@davidwengier davidwengier requested a review from a team as a code owner May 21, 2024 05:47
@dotnet-issue-labeler dotnet-issue-labeler bot added Area-IDE untriaged Issues and PRs which have not yet been triaged by a lead labels May 21, 2024
<InternalsVisibleTo Include="Microsoft.CodeAnalysis.ExternalAccess.Razor" />
<!-- Restricted IVT is direct for protocol types only -->
<RestrictedInternalsVisibleTo Include="Microsoft.CodeAnalysis.Remote.Razor" Namespace="Roslyn.LanguageServer.Protocol" Partner="Razor" Key="$(RazorKey)" />
Copy link
Member

Choose a reason for hiding this comment

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

I guess my hand is being forced, I have to write the readme of how to make breaking changes here 😆

Copy link
Contributor Author

Choose a reason for hiding this comment

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

You can reject this bit of the PR if you want, I can deal with that, but you could also just put off writing the readme until you make the first breaking change.. and then don't 😛

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-IDE untriaged Issues and PRs which have not yet been triaged by a lead
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants