Skip to content

dartdoc claims LibraryElement.== can not distinguish between non-normalized import paths #2842

Open
@jcollins-g

Description

@jcollins-g

... but the analyzer seems to handle them correctly and there is even a test for it.

Here is the claim:

// [definingLibrary] may be null if [element] has been imported or

It's possible that this was a bug that was fixed in the analyzer a long time ago, or the presence of this problem was due to the unorthodox way dartdoc used to initialize the element model, or some other bug somewhere else, or who knows.

Prove that somehow the analyzer is still responsible for this situation, or resolve/remove the various workarounds including the "unable to find defining library" warning if it is impossible.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3A lower priority bug or feature requesttype-tech-debtIssues that slow or block desirable development paths for Dartdoc, or create such problems for users

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions