Closed ryanwilsonperkin closed 2 months ago
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
View this failed invocation of the CLA check for more information.
For the most up to date status, view the checks section at the bottom of the pull request.
(Haven't contributed previously or written VSCode extensions, would appreciate any feedback from the maintainers on how best to setup for testing this)
I just saw that our CI doesn't like the code formatting...
You can run npm run format-fix
to fix the formatting
Thanks for the feedback @vogelsgesang ! Pushed some fixes
Looks good to me, thanks again!
The next release to the Marketplace will probably still be a while. In the meantime, you can get a prebuilt pre-release version from the GitHub Action artifacts
Fixes https://github.com/bazelbuild/vscode-bazel/issues/386
Relative paths for buildifier are now supported as of v0.10.0, the warning should not be shown when the buildifier executable exists at the relative path specified.
BEGIN_COMMIT_OVERRIDE fix(buildifier): Handle relative buildifier path without warning #387 END_COMMIT_OVERRIDE