We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.components.schemas.environment.properties.protection_rules (and some other places I think) is defined as:
.components.schemas.environment.properties.protection_rules
"anyOf": [ { "type": "object", "properties": { "id": { "type": "integer", "example": 3515 }, "node_id": { "type": "string", "example": "MDQ6R2F0ZTM1MTU=" }, "type": { "type": "string", "example": "wait_timer" }, "wait_timer": { "$ref": "#/components/schemas/wait-timer" } }, "required": [ "id", "node_id", "type" ] }, { "type": "object", "properties": { "id": { "type": "integer", "example": 3515 }, "node_id": { "type": "string", "example": "MDQ6R2F0ZTM1MTU=" }, "type": { "type": "string", "example": "required_reviewers" }, "reviewers": { ... } }, "required": [ "id", "node_id", "type" ] }, { "type": "object", "properties": { "id": { "type": "integer", "example": 3515 }, "node_id": { "type": "string", "example": "MDQ6R2F0ZTM1MTU=" }, "type": { "type": "string", "example": "branch_policy" } }, "required": [ "id", "node_id", "type" ] }
The examples associated with the type property seem to be used as discriminator values (although without that being spelled out explicitely anywhere).
type
I understand OpenAPIv3 has a discriminator feature for exactly that use case.
discriminator
The text was updated successfully, but these errors were encountered:
No branches or pull requests
.components.schemas.environment.properties.protection_rules
(and some other places I think) is defined as:The examples associated with the
type
property seem to be used as discriminator values (although without that being spelled out explicitely anywhere).I understand OpenAPIv3 has a
discriminator
feature for exactly that use case.The text was updated successfully, but these errors were encountered: