Fix buildifier #733
Open
Fix buildifier #733
+0
−2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
If stdin is supported by What's the root cause of it not working? I suspect when @aignas created the PR to add the linter it worked for them? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
It seems that trying to lint using stdin here is broken. I am not sure what's causing it but using a filename instead of stdin seems to fix this issue.
Funnily enough, trying to use to use stdin in the CLI works perfectly fine when I do:
~/.local/share/nvim/mason/bin/buildifier -lint warn -mode check -warnings all -format json -type build < BUILD.bazelHowever, something about the way nvim-lint is calling it seems to cause buildifier to segfault.