News for hackers. Stuff that matters.
Re:Polymer 2.4: Paving the way for 3.0 and TypeScript support by skybrian on Monday January 29, 2018 @04:49PM (#16260934)
The simple thing would be to avoid making incompatible changes to the public API. If you keep the same schema and loosen the types a bit (accepting more kinds of requests) then there's no need to have more than one schema.

But you're describing a fairly complicated scenario where you have multiple public API's with different request types, internal data (hopefully canonicalized at the border) and response types.

How do you keep track of all that data conversion without types?

There are no comments on this comment yet.