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
Hello! I love this tool. It's been an invaluable addition in my current project.
When I'm tracking down and trying to break dependency chains between bundles, it's very useful to know whether a bundle is referenced implicitly or explicitly (expanded or direct dependency) by another bundle.
I poked around in the source code, and I think I could add this feature. It's pretty straightforward to collect the data on the bundle (thanks to how the code is organized and structured). I think I could add this feature to the project, through a pull request, if it was desirable and useful.
I don't really know the best way to convey the "direct vs indirect" information, so in my case I just prepend a "+" or "-" to the bundle name. Or maybe split entries into "direct" and "indirect" tree items.
It is one piece of data that is in the build report but not this explorer tool.
The text was updated successfully, but these errors were encountered:
Hello! I love this tool. It's been an invaluable addition in my current project.
When I'm tracking down and trying to break dependency chains between bundles, it's very useful to know whether a bundle is referenced implicitly or explicitly (expanded or direct dependency) by another bundle.
I poked around in the source code, and I think I could add this feature. It's pretty straightforward to collect the data on the bundle (thanks to how the code is organized and structured). I think I could add this feature to the project, through a pull request, if it was desirable and useful.
I don't really know the best way to convey the "direct vs indirect" information, so in my case I just prepend a "+" or "-" to the bundle name. Or maybe split entries into "direct" and "indirect" tree items.
It is one piece of data that is in the build report but not this explorer tool.
The text was updated successfully, but these errors were encountered: