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

Add O# EA accessor for DocumentId.CreateFromSerialized #70229

Merged
merged 1 commit into from
Oct 4, 2023

Conversation

JoeRobich
Copy link
Member

This will replace reflection added in OmniSharp/omnisharp-roslyn#2567

@dotnet-issue-labeler dotnet-issue-labeler bot added Area-Infrastructure untriaged Issues and PRs which have not yet been triaged by a lead labels Oct 4, 2023
{
internal static class OmniSharpDocumentId
{
public static DocumentId CreateFromSerialized(ProjectId projectId, Guid id, bool isSourceGenerated, string? debugName)
Copy link
Member

Choose a reason for hiding this comment

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

what's the use case where omnisharp needs to create a doc-id from a serialized form? How does it even get the value to pass into bool isSourceGenerated? we don't expose that property public on our doc-id in the first place. Thanks! :)

Copy link
Member Author

@JoeRobich JoeRobich Oct 4, 2023

Choose a reason for hiding this comment

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

The O# navigation service can return source generated file info as part of a GoToDefinition response (See omnisharp/omnisharp-roslyn/GoToDefinitionServiceV2.cs). When this navigation item is selected by the user the client will then request the document from the server and provide it to the editor (See dotnet/vscode-csharp/SourceGeneratedDocumentProvider.ts and omnisharp/omnisharp-roslyn/SourceGeneratedFileService). So,we are round tripping the DocumentId.

Copy link
Member

Choose a reason for hiding this comment

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

i don't understand. you are undoing things to get the guid and pass that along. instead of doing that, why not actually send the DocID itself instead? i.e. instead of document.Id.Id, just send doument.Id.

Copy link
Member

Choose a reason for hiding this comment

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

@CyrusNajmabadi I think the case here is similar to what we have for LSP: we can take the document ID as a GUID and send that over the wire, and when we get it back we know it's source generated based on the URI prefix or something similar.

@JoeRobich JoeRobich merged commit 36aa45a into main Oct 4, 2023
24 checks passed
@ghost ghost added this to the Next milestone Oct 4, 2023
@333fred 333fred deleted the dev/jorobich/omnisharp-ea-documentid branch October 4, 2023 17:23
@jjonescz jjonescz modified the milestones: Next, 17.9 P1 Oct 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Infrastructure 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.

5 participants