-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Closed
Closed
Copy link
Labels
P4contributions-welcomeContributions welcome to help resolve this (the resolution is expected to be clear from the issue)Contributions welcome to help resolve this (the resolution is expected to be clear from the issue)devexp-lspIssues with analysis server's support of Language Server ProtocolIssues with analysis server's support of Language Server Protocollegacy-area-analyzerUse area-devexp instead.Use area-devexp instead.type-bugIncorrect behavior (everything from a crash to more subtle misbehavior)Incorrect behavior (everything from a crash to more subtle misbehavior)
Description
If I have a doc comment with [Directory.watch]
. I can no longer jump to definition for watch
. This is while using the analysis server with --lsp
but I suspect the regression will surface in the normal mode as well.
This worked in Dart 2.5.0. This is broken in 2.6.0
Dart 2.5.0 behavior:
- Jumping to definition on
Directory
takes you toabstract class Directory
in `directory.dart. - Jumping to definition on
watch
in comment reference takes you towatch
infile_system_entry.dart
. - Jumping to definition
watch
in non-comment usage takes you to the same place. - There are no lints for
comment_references
.
Dart 2.6.0 behavior:
- Jumping to definition on
Directory
- same. - Jumping to definition on
watch
in comment reference returns no locations. - Jumping to definition on
watch
in non-comment usage takes you to the right place. [Directory.watch]
is reported as a violation of the lintcomment_references
Metadata
Metadata
Assignees
Labels
P4contributions-welcomeContributions welcome to help resolve this (the resolution is expected to be clear from the issue)Contributions welcome to help resolve this (the resolution is expected to be clear from the issue)devexp-lspIssues with analysis server's support of Language Server ProtocolIssues with analysis server's support of Language Server Protocollegacy-area-analyzerUse area-devexp instead.Use area-devexp instead.type-bugIncorrect behavior (everything from a crash to more subtle misbehavior)Incorrect behavior (everything from a crash to more subtle misbehavior)