fix: issue unmarshalling when discriminator field is set in openapi2.0

[reversearrow]

This PR addresses issue #1010. It allows discriminator field to be of any type and case it based on the OpenAPI version.

[reversearrow]

@fenollp can please review this PR? Thanks

[fenollp]

Hi! Thanks for tackling this.

The ideal solution to me is to define a different Discriminator type in v2 and leave the current definition as is in v3. I. E. to have two different types and avoid casting.
Do you think you'd be able to update your PR with this in mind?
Thanks

[reversearrow]

Hi! Thanks for tackling this.

The ideal solution to me is to define a different Discriminator type in v2 and leave the current definition as is in v3. I. E. to have two different types and avoid casting. Do you think you'd be able to update your PR with this in mind? Thanks

Hi @fenollp, thank you for your feedback. I agree with your suggestion. After looking into the proposed approach, it seemed like it would involve significant effort to refactor. I’ve updated the PR with a simpler approach than before to address the bug. Please review and let me know what you think. I can look into implementing the suggested approach without any strict time constraints in a different PR if its still required after this PR.