You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Resolve comment references with the analyzer and retire the universal scope #4283
Dartdoc resolves comment references with its own algorithm. When the analyzer cannot resolve a reference, dartdoc falls back to searching its universal reference scope, which holds every public element, library and package dartdoc has loaded, and which is populated by crawling packages beyond the ones being documented.
Inherited documentation is handled separately, by copying the parent's comment and re-resolving its references in the inheriting class.
We want to move both to the analyzer: references should be resolved from the analyzer's element, and inherited comments should be resolved where they were written rather than where they are displayed. URLs will be built from the resolved element rather than from an internal lookup.
This will be a breaking change. References that resolve only through the fallback will stop resolving; these are reported by the analyzer's comment_references lint and most are fixed by adding a missing @docImport.
However, not everything is fixed by a @docImport. Some references will resolve to a different element under the analyzer's scoping rules (#3762), and some forms have no lexical equivalent at all — for instance a library referred to by its bare name, such as [widgets], resolves today only because every public library is registered in the universal reference scope by name, and it cannot be expressed with @docImport as it currently works (dart-lang/sdk#56528). We will work through the remaining categories as we get to them.
Activity
Require analyzer 14.5.0 and bump to 9.0.10 (#4292)
Add the doc-reference-target-differs warning (#4306)
Compare base elements and unify properties in doc-reference-target-di…