oliyh
commented
5 months ago When schemas are produced as artifacts of an application - e.g. a swagger API - they tend to fit the use cases of that application, which is good, but it also means I have to do translation to take a conceptual X from app A and give it to B, which has a different representation of the same thing.
Centrally defining them means no translation, and it also means adding a new field or whatever is likely to propagate freely whilst still guarding the system against GIGO
It's a first class description you can walk and inspect, for any purpose, rather than something you drag out via reflection from a pojo or pydantic model