bufdev

Results 35 issues of bufdev

Last night, I read Ian Lance Taylor's [commentary](https://groups.google.com/forum/#!msg/golang-nuts/6dKNSN0M_kg/EUzcym2FBAAJ) on Golang being Google's language, and it has a very poignant observation: ``` All successful languages have either a single specification or...

documentation
P3

When I run `buf mod update` with a `dep` that has no commits, I get an error message `Failure: repository has no commits` without any indication of what repository it...

For `buf breaking`, We should ignore files being deleted if `allow_unstable_packages` is try that are: - Marked as imports - Only imported by unstable packages This actually is probably somewhat...

Feature

I had a temporary `.proto` file in my home directory, and ran `buf build`, and got: ``` Failure: failed to enumerate module files: open .Trash: operation not permitted ``` I...

Feature

`protoc-gen-buf-check-{breaking,lint}` were deprecated in https://github.com/bufbuild/buf/releases/tag/v0.34.0. This was just a rename, the exact same functionality is available via `protoc-gen-buf-{breaking,lint}`. All you need to do throughout the repository is: - `s/protoc-gen-buf-check-breaking/protoc-gen-buf-breaking/` -...

Note we haven't documented it yet, but `buf protoc` is now integrated into buf, and would replace much of your logic piping the output of `buf image build -o -`...

Type: Improvement :chart_with_upwards_trend:

The Godoc says: ``` // If the error returned is due to a syntax error in the source, then a non-nil // AST is also returned. If the handler chooses...

So the BSR can pick it up. Any file in each package can have a comment on the actual `package` declaration, and the first comment by filename in alphabetical order...

Feature

We'd like to see if we can come up with something more self-describing.

Feature
Breaking Change

This field effectively has its own custom encoding to represent a field path. Instead, we should attempt to encode what we need to using Protobuf types.

Feature
Breaking Change