bufdev
bufdev
We're cleaning up our issues, and we're going to close this as a "duplicate" of #29 - we're actively working on #29, so I'd encourage you to watch that issue...
I think removing `json_name` from returned `FileDescriptorSets` is unfortunately a breaking change at this point - external plugins could totally be relying on that to remove the need to compute...
On second thought, I think it has to be the negative for backwards compatibility reasons, unless I'm confusing myself, ie `optional bool json_name_NOT_explicitly_set = 11;`. If you don't have this,...
Good point. One issue though is that makes the definition a tad weird - even if no FileDescriptorSet provider (ie protoc et al) would produce this, what does it mean...
I think it needs to be json_name_not_explicitly_set, this does matter for being able to really reason about the value of the field, see above
Note you can now use `buf generate` https://docs.buf.build/generate-usage
Hey @stevenh - thanks for the PR, but we can't consider this at the moment. This isn't an officially supported installation path, and adding it as one isn't something we...
We've seen that, but we don't think it's a good practice, and isn't one we support - we've seen numerous issues with users installing tools in this manner with dependencies...
This will be a breaking change for everyone else, no? Something should be done though, this will come up again. And protocol buffers allows use of keywords for field names,...