Skip to content

Dart docs for library don't allow CTRL + Click #59946

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

Closed
FMorschel opened this issue Jan 21, 2025 · 3 comments
Closed

Dart docs for library don't allow CTRL + Click #59946

FMorschel opened this issue Jan 21, 2025 · 3 comments
Assignees
Labels
legacy-area-analyzer Use area-devexp instead. P2 A bug or feature request we're likely to work on

Comments

@FMorschel
Copy link
Contributor

FMorschel commented Jan 21, 2025

Dart docs above library have a problem, see the following code:

/// This doc mentions everything [math], [Class], [function], [variable], 
/// [getter] and [setter].
library;

/// Here is a doc for [math]
import 'dart:math' as math;

/// Here is a doc for [Class] 
class Class {}

/// Here is a doc for [function]
void function() {}

/// Here is a doc for [variable]
int? variable;

/// Here is a doc for [getter]
int get getter => 0;

/// Here is a doc for [setter]
set setter(int value) {}

For every doc here we can CTRL + Click to go to the definition but that doesn't work on the docs above library.

CC @srawlins @DanTup


Somewhat related to #47553.

@FMorschel FMorschel added the legacy-area-analyzer Use area-devexp instead. label Jan 21, 2025
@bwilkerson bwilkerson added the P2 A bug or feature request we're likely to work on label Jan 21, 2025
@DanTup DanTup self-assigned this Jan 22, 2025
@DanTup
Copy link
Collaborator

DanTup commented Jan 22, 2025

https://dart-review.googlesource.com/c/sdk/+/405361

@FMorschel
Copy link
Contributor Author

Hopefully this will not affect that test you did but just so you know I've also added some tests about import prefix at #56931.

@DanTup
Copy link
Collaborator

DanTup commented Jan 22, 2025

At a glance, it doesn't look like there should be any conflict (in the code, or logic) between those two :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
legacy-area-analyzer Use area-devexp instead. P2 A bug or feature request we're likely to work on
Projects
None yet
Development

No branches or pull requests

3 participants