I'm now using v0.10.0 to take advantage of the ability to use a relative path for the buildifier executable, and while this does work for formatting, it still causes a warning on VSCode startup that the executable couldn't be found. I suspect that the warning check is still only looking at the system path, and isn't respecting the new relative path format.
Follow up to https://github.com/bazelbuild/vscode-bazel/issues/329
I'm now using v0.10.0 to take advantage of the ability to use a relative path for the
buildifierexecutable, and while this does work for formatting, it still causes a warning on VSCode startup that the executable couldn't be found. I suspect that the warning check is still only looking at the system path, and isn't respecting the new relative path format.