Ensuring codegen references latest Swagger spec
We use a Swagger spec to produce API client libraries from the codegen repo. Doing this required tweaking the Swagger spec that’s automatically produced by our internal API definitions, so there was some drift between the spec in the codegen repo and the one we produce automatically. We’re working to backport the changes, so our automatically-produced spec matches the one in the codegen repo. Once this work is done, we can rely on the automatically produced spec for client libraries.
Ongoing, through September 2020
Internal infrastructure improvements
We’re currently rewriting large parts of the API internals. There should be little to no external impact on API behavior, besides slight performance fluctuations.
The internals of the API had accumulated a fair bit of kludge over the past 5-10 years, so we’re rewriting a good portion of them and have identified several discrepancies in behavior across endpoints. During the rewrite, we’re learning about and ironing out many of the discrepancies that were causing friction internally — and in the process, we’re identifying further changes that we’ll implement in the future to make behaviors across the APIs more consistent.