Skip to content

Conversation

@srawlins
Copy link
Member

@srawlins srawlins commented Sep 30, 2024

There isn't much for dartdoc to be concerned with. Dartdoc basically must be aware of an exports foud in a part, and there might be reasons to be concerned with imports coming from a part. In particular, dartdoc used to skip resolving all part files when searching for libraries, just as an optimization. Can't do that any more.

This might not be a full implementation of enhanced parts support, but it sets up the basics.

Work towards #3893


  • I’ve reviewed the contributor guide and applied the relevant portions to this PR.
Contribution guidelines:

Note that many Dart repos have a weekly cadence for reviewing PRs - please allow for some latency before initial review feedback.

There isn't _much_ for dartdoc to be concerned with. Dartdoc basically must be
aware of an exports foud in a part, and there might be reasons to be concerned
with imports coming from a part. In particular, dartdoc used to skip resolving
all part files when searching for libraries, just as an optimization. Can't do
that any more.

This might not be a full implementation of enhanced parts support, but it sets
up the basics.
@srawlins
Copy link
Member Author

CC @dart-lang/analyzer-team

for (var exportedElement in libraryElement.libraryExports) {

var exported = [
...libraryElement.libraryExports,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Theoretically units provide all the exports and imports that can be in the library.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah it looks like you're right; I didn't test this with new unit tests, but they look good. Thanks

@srawlins srawlins merged commit 76678f6 into dart-lang:main Sep 30, 2024
7 checks passed
@srawlins srawlins deleted the enhanced-parts branch September 30, 2024 21:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants