1 pointby losalah8 hours ago1 comment
  • ngalaiko7 hours ago
    by drift, do you mean breaking api changes? if you control the spec, do not allow that / flag them to give clients time to update. there are plenty of tools to catch that, i.e. https://quobix.com/vacuum/commands/change-detection/
    • losalah7 hours ago
      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.

      • ngalaiko6 hours ago
        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