Automated Style Guides for REST, GraphQL and gRPC
Nov 5 · 8 min read
Ask 100 developers where a semicolon should go, and you’ll either get 100 answers, or a all-on-all fist fight. To save this from happening at work, most folks implement a style guide, which beyond helping with consistent style to avoid new developers getting shouted at for “doing it wrong”. Linters can advise best practices, shout about things which are technically allowed but likely to cause trouble, and shape the API of code as it’s being written (snake_case that method!) This is always done for code, and is becoming increasingly popular for API descriptions.


