Bazel extension does not expose an API to other extensions
gobeil opened this issue · 3 comments
gobeil commented
It's possible for extensions to expose direct execution from other VS Code extensions:
https://code.visualstudio.com/api/references/vscode-api#extensions
...but the Bazel extension does not offer any API calls (Extension.activate() does not return a value), so other extensions are forced to re-implement capabilities that are already present in the Bazel extension, such as:
- Locating the WORKSPACE file
- Watching for BUILD file changes
- Querying for targets in a BUILD file
- etc...
gobeil commented
Is there resistance to opening up such an API (worries about maintenance or backward compatibility), or would the project maintainers be happy to accept a PR that implemented it?