PPowerduck·5h agoCodegen Server Stubs vs Client SDKsHow generated client SDKs and server stubs differ.4 min read·blogs.powerduck.com
PPowerduck·7h agoCodegen Multipart Form Data BuildersHow a generated client builds a multipart upload body.4 min read·blogs.powerduck.com
PPowerduck·9h agoCodegen Abort Signal CancellationHow generated clients cancel an in-flight request.4 min read·blogs.powerduck.com
PPowerduck·11h agoCodegen Generated Retry InterceptorsHow a generated client decides what to retry and when to stop.4 min read·blogs.powerduck.com
PPowerduck·13h agoCodegen Polyglot Clients in Multiple LanguagesHow one spec feeds clients across languages without drifting.4 min read·blogs.powerduck.com
GGraphwake·1d agoContract testing without the testsMost teams never get every consumer to write contract tests. A spec diff plus one subscription per team catches breaking changes.7 min read·graphwake.hashnode.dev
GGraphwake·1d agoOrphaned API endpoints: what they are and how to find themEndpoints with no consumer on record or no owner: how to find both from your OpenAPI specs with jq, and a weekly routine to clear them.7 min read·graphwake.hashnode.dev
GGraphwake·1d agoAnatomy of a breaking change: one pull request, three teams, two alertsOne example pull request from OpenAPI change to change history: which changes break, how the score adds up, and who gets told.11 min read·graphwake.hashnode.dev
GGraphwake·1d agoHow we score the impact of an API change from 0 to 100Four public rules with caps, three bands and a worked example: the arithmetic behind Graphwake's impact score, so you can check it.3 min read·graphwake.hashnode.dev
GGraphwake·1d agoCatch OpenAPI breaking changes in pull requests with the oasdiff GitHub ActionSet up the free oasdiff GitHub Action line by line, read its output, tune it, and decide what to do with each breaking change it finds.8 min read·graphwake.hashnode.dev