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

test pr plz ignore #5634

Closed
wants to merge 20 commits into from
Closed

test pr plz ignore #5634

wants to merge 20 commits into from

Conversation

rchande
Copy link
Contributor

@rchande rchande commented Oct 1, 2015

No description provided.

jasonmalinowski and others added 20 commits October 1, 2015 15:50
TryGoToDefinition accepted a containingTypeSymbol which was used
to do some specific logic to see if third-party navigation is allowed.
Move that logic to the AbstractGoToDefinitionService and just pass the
result of the logic through.
Our INotificationService took a title and a message. In VS, the title
and message were just concatenated together on consecutive lines and
both displayed in the "message" portion of the message box. In other
hosts, we used the title as the "real" message box title. Features
were terribly inconsistent with how this was handled. Some features
expected the VS behavior (and would have had clipped text in other
hosts). Other features didn't expect the VS behavior, making ugly
dialogs.

The new behavior: the title is reserved for the title bar. This is
ignored for the VS implementation, but should just be (if anything)
the name of the feature complaining about something. All features who
actually wanted the concatenation behavior are now doing so explicitly.
It can contain modifiers or other things, so it's not just a name.
This requires some updated handling of our INavigableItem interface.
The Visual Studio implementation previously would only show the
DisplayString if it had children, and would otherwise show file
location and the source snippet. For implementations, the source
snippet is somewhat useless: in the case of methods you just see
the method signature a bunch of times. Thus, we wanted to show source
location and a fully qualified name, something which wasn't expressible.

The new interface now has DisplayString, which can be null if you want
the string to be line from the source. Whether you want to show the file
location is explicitly called out now too.
This behaves more or less exactly the same as IGoToDefinitionService.
… name right

By placing it under the IDG_VS_EDIT_GOTO menu with CommandWellOnly,
the command gets the name we want -- Edit.GoToImplementation -- but
isn't visible. We then place it where we want it to be.
@dpoeschl
Copy link
Contributor

@rchande Still needed?

@davkean
Copy link
Member

davkean commented Oct 20, 2015

Closing this as it's stale - feel free to reopen if you still need it.

@davkean davkean closed this Oct 20, 2015
mavasani added a commit to mavasani/roslyn that referenced this pull request Aug 16, 2023
… open documents.

Fixes dotnet#5634

Implemented as per dotnet/vscode-csharp#5634 (comment)

Currently, we only report local document diagnostics for open documents in the DocumentPullDiagnosticHandler. We report local and non-local diagnostics for closed documents, as well as no-location projects in the WorkspacePullDiagnosticHandler.

This change adds a new dynamically registered document diagnostic source in the public DocumentPullDiagnosticHandler with a new identifier to report non-local document diagnostics for open documents. I verified that after this change compilation end diagnostics are reported for open documents when FSA is enabled.
mavasani added a commit to mavasani/roslyn that referenced this pull request Aug 16, 2023
… open documents.

Fixes dotnet#5634

Implemented as per dotnet/vscode-csharp#5634 (comment)

Currently, we only report local document diagnostics for open documents in the DocumentPullDiagnosticHandler. We report local and non-local diagnostics for closed documents, as well as no-location projects in the WorkspacePullDiagnosticHandler.

This change adds a new dynamically registered document diagnostic source in the public DocumentPullDiagnosticHandler with a new identifier to report non-local document diagnostics for open documents. I verified that after this change compilation end diagnostics are reported for open documents when FSA is enabled.
mavasani added a commit to mavasani/roslyn that referenced this pull request Aug 16, 2023
… open documents.

Fixes dotnet#5634

Implemented as per dotnet/vscode-csharp#5634 (comment)

Currently, we only report local document diagnostics for open documents in the DocumentPullDiagnosticHandler. We report local and non-local diagnostics for closed documents, as well as no-location projects in the WorkspacePullDiagnosticHandler.

This change adds a new dynamically registered document diagnostic source in the public DocumentPullDiagnosticHandler with a new identifier to report non-local document diagnostics for open documents. I verified that after this change compilation end diagnostics are reported for open documents when FSA is enabled.
mavasani added a commit to mavasani/roslyn that referenced this pull request Aug 16, 2023
… open documents.

Fixes dotnet#5634

Implemented as per dotnet/vscode-csharp#5634 (comment)

Currently, we only report local document diagnostics for open documents in the DocumentPullDiagnosticHandler. We report local and non-local diagnostics for closed documents, as well as no-location projects in the WorkspacePullDiagnosticHandler.

This change adds a new dynamically registered document diagnostic source in the public DocumentPullDiagnosticHandler with a new identifier to report non-local document diagnostics for open documents. I verified that after this change compilation end diagnostics are reported for open documents when FSA is enabled.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants