bazel-contrib / bazel-contrib/vscode-bazel

buildifier not found even when executable path is set in settings

Open
#429 3 comments 0 reactions 0 assignees View on GitHub
type: bug
Dominant language
TypeScript
Stars
296
Forks
108
Avg merge
3d 22h
Merged PRs (30d)
5

Description

i keep getting the warnings even though i have explicitly set the path to the executable

Screenshot 2025-01-03 at 12 07 20 PM
Screenshot 2025-01-03 at 12 05 41 PM
Screenshot 2025-01-03 at 12 06 54 PM

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the warning with the executable path explicitly set in the VS Code settings, using the screenshots as the available report details. Trace the buildifier executable lookup and settings integration to determine why the configured path is ignored; done means the warning no longer appears when that executable path is valid.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vscode
Domain
devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.