bazel-contrib / bazel-contrib/vscode-bazel
Error with `tasks.json` example in README.md
- Dominant language
- TypeScript
- Stars
- 296
- Forks
- 108
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 5
Description
## versions
|thing|version|
|-|-|
|VSCode version |1.93.1|
|OS|Windows 11 + WSL2|
|VSCode Bazel Extension Version|v0.10.0|
Bazel Version|7.2.1|
## intro (you can skip this)
Hey, I've got a C++ Bazel project with lots of different targets. When I want to debug a target, I manually add entries for building and running that target (w/ CodeLLDB) into my `launch.json` and `tasks.json` respectively. I then found on your `README.md` that your extension added some commands that can be used with VSCode's `inputs` ([here](https://github.com/bazelbuild/vscode-bazel?tab=readme-ov-file#bazel-tasks)) - and thought I might see if I could write something that uses your picker to make debugging a new test target quicker (and not require editing the `launch.json`/`tasks.json` files).
## bug description
When running the [example](https://github.com/bazelbuild/vscode-bazel?tab=readme-ov-file#bazel-tasks) in the README, I get the the pop up to select a target, but when I actually select a target I get this error

> Cannot read properties of undefined (reading 'apply')
In my case this is a project inside WSL2, but I haven't tested it on just Linux or on just Windows.
Contributor guide
Research direction
Open README.md and inspect the Bazel tasks example linked in the issue. Reproduce the target selection in VS Code, then trace the example's command configuration to identify why it raises the undefined apply error. Done means the documented example selects a target and runs without that error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100