adventurous-journalist-7292012/23/2022, 2:26 PM
and tried several paths, raw or with targets, without any success. It feels unlikely to work as protos are likely to be declared with
[buf] lint_args = [ "--config buf.yaml" ]
that does not accept any other file types than
. A workaround would be to pass the yaml (or json) content of the config file directly in the config option, but it’s not really maintainable as the config grows. Any idea?
fast-nail-5540012/23/2022, 2:28 PM
adventurous-journalist-7292012/23/2022, 2:29 PM
Failure: could not read file: open buf.yaml: no such file or directory
fast-nail-5540012/23/2022, 2:31 PM
adventurous-journalist-7292012/23/2022, 2:42 PM
in pants.toml (rather than lint_args and format_args) as the config in the yaml already expects a “lint” and “format” section. My current need is repo-wide indeed, but no strong opinion to be fair, I just don’t have any example where project-only config would be better. I have also tried to declare the config file into a
target, and add it to the dependencies of my
. I would expect it to be a strong information for pants’
goal to be able to discover the config file automatically, but not quite sure it’s supposed to behave like this. I’ll open an issue then!