Ability to configure which warnings to use

[GMNGeoffrey]

It would be great if the extension allowed configuration for which buildifier warnings to use (matching the --warnings flag to buildifier).

[steeve]

even ideally, pass arbitrary buildifier flags would absolutely fit the bill

[MikeZhu92]

Definitely love to have it and be able to disable certain lint errors (for example load on top)

[kchantrell-codan]

Some of the warnings are quite egregious and don't need to be seen all the time in normal development, for instance 'print'. Currently, the only way to disable this and still use the Bazel extension is to disable buildifier completely by passing in a fake executable to the Buildifier Executable setting, e.g. /bin/false

[cj81499]

Possibly even better would be to support the .buildifier.json file.

[Simon-Chenzw]

Unfortunately, this feature is not supported yet So I created a wrapper around the binary to disable the warning this is hack

#!/usr/bin/bash

/usr/local/bin/buildifier $* --warnings=-module-docstring