-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Use list-package-dirs rather than symlinks in the analyzer #19742
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
Comments
Marked this as blocking #15103. |
De we have a time-frame for when this will likely happen? |
It's blocked on this issue, but we'd like to do it as soon as we can without breaking the ecosystem. It's the third most-starred pub issue. |
Added this to the 1.6 milestone. |
Marked as High, assigning owner. If I get this wrong, please help me by: * assigning a new owner
Set owner to @danrubel. |
Anything we can do to remove symlinks is a good thing. |
Added Started label. |
Implemented behind a flag in editor, but not tested so not enabled by default Removed this from the 1.6 milestone. |
Woo! |
What's the status on this? Is it going to be enabled by default soon? |
Not ready for 1.8 Removed this from the 1.8 milestone. |
Set owner to @pq. |
Is this still required? Tracking down everything we need for #24112 |
Nope. Closing out. Thanks! |
Pub is planning on no longer producing package symlinks (issue #15103), but currently the analyzer relies on these symlinks to resolve "package:" imports. Ultimately it would be good for the analyzer to look up packages through barback, but until then it should use "pub list-package-dirs" to find the dependency paths so pub can safely cease producing symlinks.
The text was updated successfully, but these errors were encountered: