MB
MB
> Regarding [#204 (comment)](https://github.com/trufflesuite/vscode-ext/pull/204#issuecomment-1315922516), the only thing that worries me is that if we start including tests and config files into the _Contract Explorer_, not sure how much value provides...
If integrations are not installed/enabled perhaps the greyed out options have links to their relevant docs/startup/faqs to learn more. (learn more...) link under each treeview.
I have merged in develop and @xhulz fixes to tree view. I'll use them now as my changes I made are blasted away now but its ok, I still have...
marking as draft so it doesn't get inadvertently merged right now pre-release of latest version.
I think this is pretty simple, following the code that is in there right now in the package.json its an easy addition to add a new button targeting the new...
At what level do we want to do this? Is arm/disarm globally? Or are we wanting to do this specifically per file?
we need to know which contracts are armable too? Looking for scribble annotations?
yeah makes sense, was an odd leaf node, is there much other options/elements we would want to add to these menus. Not sure what other features/options we might want in...
I have been looking/refactoring the code to make this work and if we are to remove the LocalNetworkNode we need to work on the following assumptions/rules I guess: - There...
The other option is to keep the network nodes and just remove the display of them but that might be more complex than it seems with the way the factory...