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

[Wildcard Variables] Dartdoc Support #3769

Open
Tracked by #55673
kallentu opened this issue May 10, 2024 · 3 comments
Open
Tracked by #55673

[Wildcard Variables] Dartdoc Support #3769

kallentu opened this issue May 10, 2024 · 3 comments
Labels
P2 A bug or feature request we're likely to work on type-enhancement A request for a change that isn't a bug

Comments

@kallentu
Copy link
Member

This issue will track the work needed in Dartdoc for the wildcard variables feature.

There's probably no additional work needed for Dartdoc.
However, we should test that Dartdoc isn't broken by changes to how we represent wildcard variables in the analyzer.

@kallentu
Copy link
Member Author

cc @srawlins

This issue tracks if we need anything for Dartdoc. We probably won't, but we can cross that bridge later when we have the analyzer work done :)

@srawlins srawlins added the type-enhancement A request for a change that isn't a bug label May 17, 2024
@bwilkerson bwilkerson added the P2 A bug or feature request we're likely to work on label May 22, 2024
@bwilkerson
Copy link
Member

If Dartdoc is still doing its own resolution of identifier references in doc comments, then a reference of the form [_] will need to be resolved differently. From dartdoc's perspective, this feature will only effect parameters, and that might be the only place that will be impacted by the change.

@srawlins
Copy link
Member

From dartdoc's perspective, this feature will only effect parameters, and that might be the only place that will be impacted by the change.

I think also type parameters, import prefixes, and maybe record type positional fields. In particular field formal parameters and super parameters should be tested.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 A bug or feature request we're likely to work on type-enhancement A request for a change that isn't a bug
Projects
None yet
Development

No branches or pull requests

3 participants