Support OpenAPI 3.0 discriminator.mapping
What issue does this pull request resolve? resolves https://github.com/ajv-validator/ajv/issues/2003
What changes did you make? option to ignore additional mappings for discriminator. Mappings are not needed in AJV, but they are passed from OAS and should be ignored.
Is there anything that requires more attention while reviewing? The provided documentation
@epoberezkin could you check this PR?
@epoberezkin Any update on this one? I'm about to implement a work-around using extensions and jq to transform the spec (since oapi-codegen requires the mappings object, but it would be nice to be able to produce a spec that doesn't require these extensions.
I've been running into this issue as well--is this being reviewed/considered for approval?
I have to use patch as a workaround while it is not approved
@epoberezkin bump on this! Seems like a feasible solution
Hi @jeffmay or @VolodymyrMachekhin, could you explain how you applied the work around?
Hi @jeffmay or @VolodymyrMachekhin, could you explain how you applied the work around?
probably using this: https://www.npmjs.com/package/patch-package
Came across this as Pydantic generates discriminator.mapping for all union types, would be great to have this merged!