Option to disable example pre-population in Try It Out feature

I would like the option to disable pre-populating examples from the spec for OAS 3.0

I have a GET request that allows filtering by many different parameters. When the user clicks 'Try it out' ALL the parameters are pre-populated. There are never any results, due the the sheer number of filtering options selected.

If the user wants to make any meaningful request, they must first go in and remove every single example.

This seems to have been the default for Swagger 2.0, but OAS 3.0 does not seem to have an option.

I've tried changing various settings without success.

The only thing that works is changing the definition from OAS 3.0 to Swagger 2.0. But this obviously isn't a workable solution.

When the spec is defined as OAS 3.0:

{
  "openapi": "3.0.0",
  "paths": {...}
}

When the spec is defined as Swagger 2.0:

{
  "swagger": "2.0",
  "paths": {...}
}

Notes:

• The rest of the spec and all settings remain unchanged in the examples above.

Start with docs/usage/configuration.md and the supportedSubmitMethods configuration referenced in the issue, then reproduce the Try It Out behavior with the provided OAS 3.0 and Swagger 2.0 examples. Done means users can configure OAS 3.0 requests so examples are not pre-populated, while existing behavior remains available when desired.