Skip to content
New issue

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

'allowEmptyValue' doesn't work if parameter is 'required'. #5129

Closed
mkrup opened this issue Jan 17, 2019 · 4 comments · Fixed by #5142
Closed

'allowEmptyValue' doesn't work if parameter is 'required'. #5129

mkrup opened this issue Jan 17, 2019 · 4 comments · Fixed by #5142

Comments

@mkrup
Copy link

mkrup commented Jan 17, 2019

Swagger UI version is 3.20.5.
I expect that everything should work as in #1934 in the described case but it doesn't.
Swagger UI does not allow to send a request when 'required' parameter is also 'allowEmptyValue'.

@shockey
Copy link
Contributor

shockey commented Jan 19, 2019

Regression confirmed:

openapi: "3.0.0"

paths:
  /:
    get:
      parameters: 
      - name: one
        in: query
        allowEmptyValue: true
        required: true
        schema:
          type: string
      responses:
        200:
          description: ok

PS: @mkrup, please follow the issue template next time 😄

@shockey
Copy link
Contributor

shockey commented Jan 29, 2019

Fixed! Will be released later this week.

@shockey
Copy link
Contributor

shockey commented Jan 29, 2019

thanks for the report, @mkrup!

@mkrup
Copy link
Author

mkrup commented Jan 30, 2019

Great, thank you!

@lock lock bot locked and limited conversation to collaborators Jan 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants