-
Notifications
You must be signed in to change notification settings - Fork 44
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
Updated tag detection for packages without a primary library. #592
Conversation
Thank you @isoos! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for looking into this!
LGTM for the short-term, but ideally we should recognise packages that are mainly executable and have another tagging scheme for them, or at least use their declared executables from the pubspec as root libraries.
I'm not entirely sure that we should treat them that much different on this stage of the analysis. E.g. in case of Of course we should also tag "binary-only" status, which would change the instructions on the "Install tab"... |
You can, but the convention is to not import internals, and I don't think we should provide an analysis that suggests what works in case you break the convention. |
That's a good point. Should I remove the |
Could you look up the executables, and use those in case there are nothing in lib/ ? |
I've updated the PR, checking the
|
Fantastic! Any chance you could push out a release with this fix? Much appreciated! |
@pq: Unfortunately there are no production deployments around the holidays, I'd expect this to get into prod in early January. |
No worries. That makes perfect sense. Hope you enjoy some time off! ❄️ |
lib/*.dart
. However, if there is a primary library in the package (/lib/[package_name].dart
), it will be used as a single value in top-level libraries.