You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Allow accessing files outside of "lib" inside Dependencies tree #1590
If you open it as its own folder (either in a new window, or even as an additional analysis root in for the current window) it doesn't resolve its own dependencies, and therefore everything has squiggles:
(it also tries to prompt you to run pub get, though I could fix that).
I think this is because without a .packages file, it doesn't know where to get these packages from (whereas inside your own project, the .packages file has all transient dependencies).
So maybe the only way to handle this would be to do your original suggestion, which is to allow the tree to render from the root of the package instead of its lib folder. Or, we could add the folder to the VS Code workspace and exclude it as an analysis root.
I'll come back to it after doing #1591 to see if anything better comes to me.
allow the tree to render from the root of the package instead of its lib folder. Or, we could add the folder to the VS Code workspace and exclude it as an analysis root.
Any option would be useful for me, but I think that it would be nice to have both options for the plugin in order to extend the usefulness for the most users possible
changed the title [-]Add an option to open a dependency package[/-][+]Allw accessing files outside of "lib" inside Dependencies tree[/+]on Nov 18, 2020
changed the title [-]Allw accessing files outside of "lib" inside Dependencies tree[/-][+]Allow accessing files outside of "lib" inside Dependencies tree[/+]on Nov 18, 2020
Activity
Add the ability to open packages in VS Code from the Dependencies view
DanTup commentedon Apr 16, 2019
I implemented this:
However I found a problem:
If you open it as its own folder (either in a new window, or even as an additional analysis root in for the current window) it doesn't resolve its own dependencies, and therefore everything has squiggles:
(it also tries to prompt you to run
pub get, though I could fix that).I think this is because without a .packages file, it doesn't know where to get these packages from (whereas inside your own project, the .packages file has all transient dependencies).
So maybe the only way to handle this would be to do your original suggestion, which is to allow the tree to render from the root of the package instead of its lib folder. Or, we could add the folder to the VS Code workspace and exclude it as an analysis root.
I'll come back to it after doing #1591 to see if anything better comes to me.
Rodsevich commentedon Apr 16, 2019
Nice! 😄
Any option would be useful for me, but I think that it would be nice to have both options for the plugin in order to extend the usefulness for the most users possible
[-]Add an option to open a dependency package[/-][+]Allw accessing files outside of "lib" inside Dependencies tree[/+][-]Allw accessing files outside of "lib" inside Dependencies tree[/-][+]Allow accessing files outside of "lib" inside Dependencies tree[/+]DanTup commentedon Nov 18, 2020
The tree now starts one level up from where the package resolves, if the resolved folder is called "lib":