Currently buildifier is executed from the disk root, which means that if you configure a path like "bazel.buildifierExecutable": "./path/to/buildifier" then the extension will execute /path/to/buildifier - which likely doesn't exist.
It would be good if the CWD for the execution could be set to the workspace root to enable relative path config. This is similar to #132 but doesn't require any variable resolution.
Currently buildifier is executed from the disk root, which means that if you configure a path like
"bazel.buildifierExecutable": "./path/to/buildifier"then the extension will execute/path/to/buildifier- which likely doesn't exist.It would be good if the CWD for the execution could be set to the workspace root to enable relative path config. This is similar to #132 but doesn't require any variable resolution.