Skip to content

docs: Add blank defaults for optional enums#75

Open
johnchaffee wants to merge 1 commit intotwilio:mainfrom
johnchaffee:enum-defaults
Open

docs: Add blank defaults for optional enums#75
johnchaffee wants to merge 1 commit intotwilio:mainfrom
johnchaffee:enum-defaults

Conversation

@johnchaffee
Copy link

When rendering this spec in Swagger UI, the first item in the enum is getting selected by default and causing errors in some cases (e.g.message_enum_schedule_type of fixed fails unless you are sending a scheduled message). Setting the default to blank solves it.

When rendering this spec in Swagger UI, the first item in the enum is getting selected by default and causing errors in some cases (e.g.`message_enum_schedule_type` of `fixed` fails unless you are sending a scheduled message). Setting the default to blank solves it.
@childish-sambino
Copy link
Contributor

This issue has been added to our internal backlog to be prioritized as it changes generated configuration. +1s on the issue summary will help it move up the backlog (DI-2363).

@childish-sambino childish-sambino added status: work in progress Twilio or the community is in the process of implementing type: twilio enhancement feature request on Twilio's roadmap code-generation issue deals with generated code labels Sep 30, 2022
@childish-sambino childish-sambino added status: work in progress Twilio or the community is in the process of implementing status: waiting for feature feature will be implemented in the future and removed status: work in progress Twilio or the community is in the process of implementing labels Nov 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

code-generation issue deals with generated code status: waiting for feature feature will be implemented in the future type: twilio enhancement feature request on Twilio's roadmap

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants