98c02851c8
Use targetted ignore comments for the cases where we are bound by backward compatibility. I've left some file based linters, especially when the file is riddled with linter voilations (e.g. enum names), or if it's a property of the file (e.g. package and file names). I encountered an odd behavior related to RPC_REQUEST_RESPONSE_UNIQUE and RPC_REQUEST_STANDARD_NAME. Apparently, if they target a `stream` type, we must separate them into separate lines so that the ignore comment targets the type specifically. |
||
---|---|---|
.. | ||
README.md | ||
buf.gen.yaml | ||
buf.yaml |
README.md
Buf
buf
is a high-performanceprotoc
replacement.
Installation
See installation instructions here.
Usage
make proto
in the root of this repo will invoke buf
using the configuration in this directory.
Why use buf
instead of protoc
?
Buf is a user-friendly tool to work with Protobuf that outperforms protoc
in every conceivable way. It was written by the author(s) of prototool
, another tool that made generating Protobuf easier, but which is now deprecated in favor of buf
. Buf also does linting and breaking-change detection.