bufdev
bufdev
We're going to potentially be making changes to tags to allow this in the near future. Will keep this issue open as we update you on that.
@tv42 I have to second this one, big time. For comparison, I wrote a "reference" fuse implementation that is effectively a pass-through to the OS file system, and I've only...
Yes, `buf` considers this a breaking change - there's no way for `buf` to know that you intended to rename `foo.A` to `bar.A` - if you can come up with...
I chose to test out a quick fix for this, itself which would have massive implications that we would need to carefully think about: ```diff diff --git a/private/pkg/storage/storageos/bucket.go b/private/pkg/storage/storageos/bucket.go index...
Yea we should definitely do this. This annoys me too.
This has been implemented in #3124 and will go out in the next release. Feel free to watch this repository to get updates on when the release goes out!
`buf` does not do introspection on actual message field types - `buf` assumes that changing the type of a field is a breaking change. We could in theory go further...
We're going to close this as stale, as I don't think this is an update we're going to be able to staff unfortunately. Apologies.
Actually on second thought, this might be something we want to do. But going to keep this issue closed in favor of https://github.com/bufbuild/buf/issues/2318.