bufdev
bufdev
There's two things mentioned here: (1) with `build.excludes = ["a"]`, `buf ls-files` returns no values. (2) with `build.excludes` empty, `buf build` complains of duplicates. (1) is somewhat by design, to...
I think doing this detection is outside our scope of allocatable work, unfortunately. Closing this as stale, but can discuss more.
Ignore promoting `buf beta registry webhook` for now
Buf is currently working on custom lint and breaking change plugins, as well as an SDK to author plugins in Go, which API-linter's rules will fit very easily into. After...
In theory, I like it. However, there is an issue with name conflicts. What happens if you have: ```proto // a/a.proto package a; message One {} ``` ```proto // b/b.proto...
Adding a new field to a `oneof` isn't something we would consider breaking, and the buf CLI takes a strict stance that it only will print errors from `buf lint`...
Closing since we can't reproduce, but if you can provide us a reproducible example, we're happy to look into it!
You'll have to provide us a specific, reproducible example, and then we'd be happy to investigate. Let us know!
What we're looking for: - The code, in a consumable manner such as a temporary github repository, that we can inspect and build ourselves - What you see - What...
Thanks for your request here. It's a fair issue, but we'll have to consider the implications. We are working on the ability to write custom lint plugins at the moment,...