Q&A (please complete the following information)

• Method of installation: [npm, dist assets]
• Swagger-UI version: [>=3.25.1]
• Swagger/OpenAPI versi

Is your feature request related to a problem

Coming from this issue: tiangolo/fastapi#817

The docs have some sections with functions using *, in the parameters.

It is explained here: https://fastapi.tiangolo.com/tutorial/path-params-numeric-validations/#order-the-parameters-as-you-need-tricks

But in other sections like: https://fastapi.tiangolo.com/tutor

Description

Need support for Ssource code annotation to specify a different endpoint or URL in swagger documentation (swagger.json) from actual specified in code via @path?

Just a FYI when people start trying to submit bugs about this, mobx-react shipped a funky build which is causing broken-ness (at least when using redoc-cli bundle)

mobxjs/mobx-react#831

Currently breaks with an error like:
Cannot find module '..../.npm/_npx/1868/lib/node_modules/redoc-cli/node_modules/mobx-react/dist/mobxreact.js (added for searchability)

Can

First of all, the following repository has all the code (and description as well) to reproduce this problem: https://github.com/elgleidson/swagger-problem

I have the following JSON:

{
  "nonNullableField": "not null",
  "nullableField": null,
  "nonNullableObjectField": {
    "someField": "some value"
  },
  "nullableObjectField": null,
  "nonNullableList": [
    "not null"

There is absolutely no documentation (other than "this is how you drop an existing file". What is the point of releasing such a product if you do not document it?

Bug Report Checklist

• Have you provided a full/minimal spec to reproduce the issue? not relevant
• Have you validated the input using an OpenAPI validator (example)? not relevant
• What's the version of OpenAPI Generator used?
• Have you search for related issues/PRs?
• What's the actual output vs expected output?

This is more of a development problem and does not affect users as it is with dev dependencies. When cloning the repository and running yarn, yarn warns about incorrect peer dependencies:

$ git clone https://github.com/apiaryio/dredd.git dredd-clean
Cloning into 'dredd-clean'...
remote: Enumerating objects: 54, done.
remote: Counting objects: 100% (54/54), done.
remote: Compressin

It would be nice to have a note or two on which OAS versions this project supports.
Similar to https://github.com/swagger-api/swagger-ui/#compatibility

cc @webron

The official API docs are here

https://developers.google.com/maps/documentation/geocoding/start

I wanted to know if it would be possible to add this API's Swagger doc (and that of similar Google APIs like this).

When I run the sample from https://github.com/marshmallow-code/apispec/blob/dev/docs/quickstart.rst

the expected output

# {'components': {'parameters': {},
#                 'responses': {},
#                 'schemas': {'Gist': {'properties': {'id': {'format': 'int64',
#                                                            'type': 'integer'},
#                                

Is your feature request related to a problem? Please describe.
This project looks amazing, but I´m somewhat left with a no-clue of how I´m supposed to build up an API using this repository after the initial look. Is there any user guides about where to configure what and what to configure?

Describe the solution you'd like
Documentation with a walkthrough of how-to, for instance, deplo

"Require calls will work only in Node.js, and will cause errors for anyone trying to use the ruleset in the browser. If your ruleset is definitely going to only be used in the context of NodeJS then using them is ok, but if you are distributing your rulesets to the public we recommend avoiding the use of require() to increase portability."

I have a extensions.js file that has functions I reuse

I am trying to generate Golang code for following openapi 3 spec. I have doubts regarding Go code generation for enum related types.

openapi: "3.0.0"
info:
  version: 1.0.0
  title: Swagger Petstore
  description: A sample API that uses a petstore as an example to demonstrate features in the OpenAPI 3.0 specification
  termsOfService: http://swagger.io/terms/
  contact:
    nam

• Guidance on adding a linter new rule-action (if none of the existing ones can perform the action, or be extended)
• Expand on guidelines re: keeping commits to logical areas of the code / individual packages where possible
• Use of conventional-commit standard going forward
• Advice not to include any package-lock.json changes PRs, for security reasons. File will be regene

Based on #32 and discussion with @Hultner

• Have a smaller quickstart
• Link to docs in the top of the page (not only badge)
• Move documentation content to a separate document
• Share roadmap info
• Examples of errors that could be found
• Possible workflows for Schemathesis. As a part of a test suite, CI step, CLI, etc
• [Usage](https://github.com/untitaker/

I've really enjoyed using the tool for my project documentation.

In addition to API specs, however, I'm also hosting a lot of general software design documentation (that doesn't involve REST API paths at all, like class overview, state diagrams, execution concept & flow, etc.) using Markdown. Right now I'm using tags + x-tagGroups, where the description field for some tags can be hundreds an

Hello

First of all, thank you open-sourcing your code, I understand it is not easy to maintain in wild public. I am deciding which mock server generator from OpenAPI v3 specification to use and "motivation" section in readme would really help people like me to choose.
I am expecting form such docs section to get insight why you created new library instead of using already existing solutions

"false".equalsIgnoreCase(defaultValue) should be "false".equalsIgnoreCase(example)

...
            } else if (BooleanProperty.TYPE.equals(type)) {
                if ("true".equalsIgnoreCase(example) || "false".equalsIgnoreCase(defaultValue)) {
                    return Boolean.valueOf(example);
                }
            }
...

Looking for help to improve the examples READMEs, particularly examples/3-eov-operation READMEs

When generating a collection from the attached YAML spec, the POST body is expected to comply with the supplied definition of ApplicationInstance.

Instead, the generated request body solely contains the value of the "description" attribute.

Failing_body_ref.zip

Tested in PostmanCanary 7.1.1-canary06.