Does it make sense to apply Required to a response schema field?
Up until now, I have set Required=true only for request schema fields. For response schema fields that I know won't be populated with null, I have set Nullable=false. Now, for the sake of Microsoft's AutoRest tool and the code it generates, I am being asked to set Required=true as well as Nullable=false for response fields. Does this make sense semantically? To my mind, it doesn't. I know you can set Request=true for response fields, but does it make sense to do so?
Generation of Schema from API specification for model definition
I understand the model definition is part of Open Api specification, but this definition just helps in reference and not usable at all both for consumers and provider. Just like we can generate the code stub from the specification it will be great if we can generate schema definition in json schema with the versions.
