Investigate if there is a room for a better OAS configurability or for a better default generations e.g.
- Better examples, schemas, descriptions
- Other OAS sections according to the Spec
Reflect in the Documentation if there are changes.
The downside of this approach is that every Resource/Relationship will generate the whole set of unique Schemas.
Think twice whether keep decent enough generic level of OAS (with less number of Schemas) or make it super precise but with a huge amount of custom OAS Schemas.
Investigate if there is a room for a better OAS configurability or for a better default generations e.g.
Reflect in the Documentation if there are changes.
The downside of this approach is that every Resource/Relationship will generate the whole set of unique Schemas.
Think twice whether keep decent enough generic level of OAS (with less number of Schemas) or make it super precise but with a huge amount of custom OAS Schemas.