Paul Bethe
Paul Bethe
current hack: buildozer does accept input on stdin which it writes to stdout. Problem if there is a BUILD and WORKSPACE file in //, how does buildozer distinguish? Maybe a...
ah, that could work, then it could just be `//__workspace__:com_google_absl` @laurentlb what do you think?
It looks like there is a function DictionarySet in edit.go but no commandline trigger to use that in edit/buildozer.go Feel free to add and send a PR
@laurentlb -- thoughts?
what problem does this solve that some combination of: tables.go and jsontables doesn't already solve in combo with `# buildifier: do not sort` ?
What is your example, and why do you want this? There are a few rules in: https://github.com/bazelbuild/buildtools/blob/195b83e94906df245fdc44da27b1be5489087025/build/rewrite.go including 'buildifier: leave-alone' will that handle your case?
by default NumIO = 200 -- you can probably work around this for now by setting -numio=20 or something similarly low. The fix is presumably to throttle the calls to...
typically the way you would deal with this is concatenation. instead of ``` deps = [ ":a", requirement("requests"), ":b", ], ``` split into two lists ``` deps = [ ":a",...
that is fair. do you think this should sort as [ ":a", ":b", requirement("requests"), ], Alphabetical, ignoring " ?
This change does seem reasonable and worth considering, but note that internally it will require a depot-wide change so will have to be rolled out cautiously.