News for hackers. Stuff that matters.
Re:Ask HN: How do you catch OpenAPI drift before the UI breaks? by losalah on Wednesday March 04, 2026 @04:49AM (#47245258)
By “drift” I don’t just mean breaking changes between spec versions.

I mean the spec and the live API behavior fall out of sync (often because implementation changes land first and the spec lags, or vice-versa). The first time we notice is when a real UI flow breaks and someone has to spelunk Devtools to see what the server actually returned (missing fields, nullability changes, new enum values, shape differences...)

So spec-diff tools like Vacuum help once you’re comparing two OpenAPI files, but my pain is earlierm catching “spec vs reality” from normal dev/staging usage (real accounts + data) and getting an actionable report (which operation, what mismatch, request id/response snippet) before it turns into a broken UI + an hour of debugging.

Re:Ask HN: How do you catch OpenAPI drift before the UI breaks? by ngalaiko on Wednesday March 04, 2026 @05:42AM (#47245670)
did you consider using code-generators to make sure spec and implementation are aligned?

openapi is really meant to be either generated from code, or server-code is meant to be generated from openapi spec