Does anyone know a way to read the IssueCollections provided by other extensions?
Extensions can send data between each other using the CommandsRegistry
invoke() API, as long as the destination extension defines some command that can be invoked by others as an API. But it needs to be explicitly defined by that extension, as we really do not want extensions touching each others’ state unexpectedly.
Thanks. I perfectly understand and agree with the sandboxing concept. My use case would have been to see if there are any linting errors without running a linting process myself. So, only reading the issues (if any at all).