bufdev

We don't have a super-concrete use case for having a `buf.validate.Violations` message, as opposed to using lists of `buf.validate.Violation` messages. There's a thought that we may want a repeated message...

We're looking to delete `buf.validate.Violations` in https://github.com/bufbuild/protovalidate/issues/96, and it would also be nice for the Golang API to not hard-depend on a specific version of the Protobuf API. To do...

Add managed module: `buf.build/google/gnostic`

3

## Mandatory **Where is the source code for the Managed Module?** https://github.com/google/gnostic Specifically the `openapiv3` directory, but also maybe the `openapiv2` directory. **Do the proto files declare a package?** Yes,...

I'm not yet sure if we want to add this into mainline. Opening this for discussion. This is re: https://github.com/bufbuild/buf/issues/2986. This adds a `STABLE_PACKAGE_NO_IMPORT_UNSTABLE` lint rule, with no category, that...

Add buf convert --disallow-unknown

2

Begins https://github.com/bufbuild/buf/issues/2714. See https://github.com/bufbuild/protoyaml-go/issues/37 for the remaining work for YAML that once fixed, can resolve the aforementioned issue.

Add DiscardUnknown to UnmarshalOptions

1

Similar to: - https://pkg.go.dev/google.golang.org/[email protected]/proto#UnmarshalOptions - https://pkg.go.dev/google.golang.org/[email protected]/encoding/protojson#UnmarshalOptions - https://pkg.go.dev/google.golang.org/[email protected]/encoding/prototext#UnmarshalOptions It would be good to have a `DiscardUnknown` option on `protoyaml.UnmarshalOptions`. https://github.com/bufbuild/buf/issues/2714 is the motivation for this issue.

This is a write-only property that has nothing to do with the `BufYAMLFile` interface and what this object is. We need to rewrite https://github.com/bufbuild/buf/pull/3181 so as to not add this...

Make buf generate --clean a per-plugin option that does a "smart" clean

1

See https://github.com/bufbuild/buf/pull/3124#issuecomment-2209407669 for an explanation.

- If `len(fields) < 6`, I want all fields to appear on one line. - If there is only `fields` and no `required`, I want the whole thing on one...

We have a note on `slicesext.ToStructMapOmitEmpty`: https://github.com/bufbuild/buf/blob/705a37b0f358afe70e347cb01c6bab5f6bb423fe/private/pkg/slicesext/slicesext.go#L149 We likely did this to make sure we didn't edit existing behavior, but I bet if we go through `buf` and `core`, we...