bazel-contrib / bazel-contrib/vscode-bazel
Bazelrc Language Server
- Dominant language
- TypeScript
- Stars
- 296
- Forks
- 108
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 5
Description
I started a [language server for bazelrc files](https://github.com/salesforce-misc/bazelrc-lsp) a while ago. By now it is slowly getting into a state where it might be useful for a wider audience.
I am wondering: Should we integrate the bazelrc language server also into this Bazel extension? Or publish it as a separate extension? I would tend towards "separate extension" since this makes it easier to provide new releases, keep bug backlogs separate etc.
But apparently, there was an earlier effort to merge various Bazel extensions into this uber-extension here. I don't know about the motivations of this merge. Can somebody elaborate on those original motivations and provide some guidance on whether to publish `bazelrc-lsp` as a separate extension to the VS-Code market place
Contributor guide
Research direction
Read the linked bazelrc-lsp project and this extension's history of merging Bazel extensions; the issue provides no file or test entry point. Done would be a documented decision and guidance on whether bazelrc-lsp belongs in this extension or should be published separately.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100