swagger_parser uses try catch of each variant to handle oneOf in an openapi spec and in doing so probably doesn't confirm tag values. First confirm if this is a problem using end-to-end testing of documented route <=> dart client and add this testing to CI. If it is, determine the best approach to resolution: properly handling tags in swagger_parser? adding and enforcing the exisint of discriminator field in union types of generated openapi specs? something else?
Note the swagger_parser is already being patched in a fork because it also fails to rename the classes it uses to represent unions properly, resulting in import issues.
swagger_parser uses try catch of each variant to handle
oneOfin an openapi spec and in doing so probably doesn't confirm tag values. First confirm if this is a problem using end-to-end testing of documented route <=> dart client and add this testing to CI. If it is, determine the best approach to resolution: properly handling tags in swagger_parser? adding and enforcing the exisint ofdiscriminatorfield in union types of generated openapi specs? something else?Note the swagger_parser is already being patched in a fork because it also fails to rename the classes it uses to represent unions properly, resulting in import issues.