Optional array query params with enum are always sent after try out with non empty params

Q&A (please complete the following information)

• OS: macOS
• Browser: chrom
• Version: Chrome Version 72.0.3626.96 (Official Build) (64-bit)
• Method of installation: https://editor.swagger.io/
• Swagger-UI version: Not sure
• Swagger/OpenAPI version: OpenAPI 3.0

Content & configuration

Example Swagger/OpenAPI definition:

openapi: '3.0.0'
info:
  description: >-
    Repro API
  title: Repro API
  version: '1.0'
paths:
  /test:
    get:
      summary: Test get
      parameters:
        - name: fields
          in: query
          required: false
          allowEmptyValue: false
          schema:
            type: array
            items:
              type: string
              enum:
                - friends
                - family
          example:
            - friends
          style: form
      responses:
        200:
          description: Success!
          content:
            application/json:
              schema:
                type: object
                properties:
                  id:
                    type: integer
                  name:
                    type: string

Swagger-UI configuration options:

Not sure; default?

No QueryStringConfig

Describe the bug you’re encountering

To reproduce…

Steps to reproduce the behavior:

1. Click on ‘GET /test Test get’
2. Click on ‘Try it out’
3. Deselect “friends” by command+click; Or select ‘–’
4. Click on ‘Execute’
5. Check ‘Request URL’

Expected behavior

Expect ‘Request URL’ being: https://editor.swagger.io/test

Screenshots

Additional context or thoughts

This issue is similar to but different from #4223. There will be no problem if array items don’t have enum. The example is not required. It is there just to give a non-empty value to start with. As mentioned in the title, I do need to do a try out with some value(s) like “friends” if there is no example. In another word, it seems I couldn’t clear the field after the first, non-empty, try out.

[h4sohail]

This issue forced us to modify our validation and allow an empty string (which is a sort of a hack) as a query param, it would be great if selecting “–” option would just simply not send that param instead of sending it empty.

[pyce-lb]

@h4sohail as a work around you can Ctrl+Left Click on any previously selected values to unselect them, nevertheless I agree with your suggestion:

it would be great if selecting “–” option would just simply not send that param instead of sending it empty.