Ability to define schema name for nested objects in requests #607
manuel-watchenterprise
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
It can be personal taste to have everything in schemas but when it comes to code generators with hardly typed languages such as dart and java, it is almost required to have this option, otherwise ugly automatic names will appear in the application code. Also, it prevents duplications as multiple endpoints can return the same but all of them will have the full specification as it is not using schemas.
Would be nice to understand multiple levels and arrays.
I don't think it's Scramble's responsibility if these extra properties are different in various requests. The first occurrence defines the schema and any reference to the very same schema should use that regardless what is in the request.
However, recognising such a situation can be handy, obviously.
Beta Was this translation helpful? Give feedback.
All reactions