fix(buildifier_availability): specify lint mode to override default #483
+1
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
buildifer allows you to configure defaults by placing a
.buildifer.jsonfile at the root of the project.If this file happens to have
then the extension will run into an error at startup which presents a confusing "Failed to find a Bazel workspace" error dialog to the user. From the Extension Host logs in the Output panel:
since the command in buildifer_availability is just to check that buildifier is present and able to return JSON output, the default from the config file can be overridden to prevent this error.