fix: Handle relative buildifier path without warning

[ryanwilsonperkin]

Fixes #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

[google-cla]

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.

[ryanwilsonperkin]

(Haven't contributed previously or written VSCode extensions, would appreciate any feedback from the maintainers on how best to setup for testing this)

[vogelsgesang]

Thanks for your contribution and for the bug report!

A couple of stylistic issues, but on a high-level you found the right place to fix this 🙂

Regarding testing: We currently don't have a good testing strategy, yet. In #366, I am about to introduce the first unit tests, but we are still far away from a satisfactory testing solution, and I don't want to put it on you to build that infrastructure for the overall project. Hence, I would be fine merging this without test cases

[vogelsgesang]

I just saw that our CI doesn't like the code formatting...
You can run npm run format-fix to fix the formatting

[ryanwilsonperkin]

Thanks for the feedback @vogelsgesang ! Pushed some fixes

[vogelsgesang]

Looks good to me, thanks again!

[vogelsgesang]

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