Skip to content

Exported extensions don't show up in the docs for a library #2032

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
Tracked by #39049
natebosch opened this issue Oct 3, 2019 · 5 comments · Fixed by #2045
Closed
Tracked by #39049

Exported extensions don't show up in the docs for a library #2032

natebosch opened this issue Oct 3, 2019 · 5 comments · Fixed by #2045
Labels
P1 A high priority bug; for example, a single project is unusable or has many test failures

Comments

@natebosch
Copy link
Member

I'm working on dart-archive/stream_transform#83

When I generate docs I see all the deprecated top level methods that are exported from the "main" library, but none of the extensions. If I add an extension directly I do see it in the docs.

@keertip
Copy link
Collaborator

keertip commented Oct 3, 2019

@jcollins-g , could you take a look? Thanks!

@jcollins-g jcollins-g added the P1 A high priority bug; for example, a single project is unusable or has many test failures label Oct 4, 2019
@mkustermann
Copy link
Member

@jcollins-g This might be a blocker for D26, since all our tools need to support extension methods and the core libraries, dart:ffi in particular, are using extension methods now.

@jcollins-g
Copy link
Contributor

Extensions should show up in their dartdoc canonical locations which may or may not be the same as their defined locations. Will investigate.

@jcollins-g
Copy link
Contributor

Getting this correct is turning out to be more of a pain than I realized. Some discovery support is best implemented as analyzer code and I've got the beginnings of that working now.

@jcollins-g
Copy link
Contributor

This has improved, but there are still significant bugs, see #2047.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 A high priority bug; for example, a single project is unusable or has many test failures
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants