We are having code gen issues when using oneOf in a recent schema and finding duplicate classes are being generated by nSwagstudio when the oneOf is part of the schema instead of the query.
Example: Here the query references the schema
and the schema is defined using oneof:
We were able to resolve this by moving the mapping to the query but I wanted to check if both scenarios were valid and if it is a codeGen issue rather than a schema issue
But we should be able to use the original definition as it is correct per openAPI specifications.
Hello,
We are having code gen issues when using oneOf in a recent schema and finding duplicate classes are being generated by nSwagstudio when the oneOf is part of the schema instead of the query.
Example: Here the query references the schema
and the schema is defined using oneof:
We were able to resolve this by moving the mapping to the query but I wanted to check if both scenarios were valid and if it is a codeGen issue rather than a schema issue
But we should be able to use the original definition as it is correct per openAPI specifications.