Thanks to visit codestin.com
Credit goes to Github.com

Skip to content

Consider having the explicit discriminator field in Client v2 representations #45047

@vmuzikar

Description

@vmuzikar

If having the protocol field not be part of the schema is causing it to be parsed into the additionalFields, perhaps we should just have it as a proper field.

Originally posted by @shawkins in #44727 (comment)

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions