Menu

Post image 1
Post image 2
1 / 2
0

Moving our gRPC linting from buf 1.35 to custom protoc plugins: enforcing API standards

DEV Community·ANKUSH CHOUDHARY JOHAL·about 1 month ago
#plPVnzgj
#developer#moving#grpc#linting#protoc#proto
Reading 0:00
15s threshold

After 14 months of fighting buf 1.35's rigid linting rules that generated 127 false positives per 1000 lines of protobuf, our team of 12 backend engineers migrated to a suite of custom protoc plugins that cut false positives by 82%, reduced linting time by 64%, and let us enforce API standards that buf's built-in rules couldn't touch. 📡 Hacker News Top Stories Right Now How fast is a macOS VM, and how small could it be? (44 points) Why does it take so long to release black fan versions? (294 points) Why are there both TMP and TEMP environment variables? (2015) (50 points) Show HN: DAC – open-source dashboard as code tool for agents and humans (28 points) Show HN: Browser-based light pollution simulator using real photometric data (19 points) Key Insights Custom protoc plugins reduced linting false positives from 12.7% to 2.3% across 42 production protobuf repos buf 1.35's linting rules are limited to 47 built-in checks, while our custom plugin suite supports 192 configurable rules Linting CI time dropped…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More