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? Please describe.
Deployed Parse server using k8 and used /parse/health for the readinessProbe and livenessProbe probe. But when deploy new code and broke the database connection, /parse/health still returns 200 OK. So old container was killed and new broken one brought online

Describe the solution you'd like
Only return 200 ok after db is

Your example of a well structured URL:

https://api.contoso.com/v1.0/people/jdoe@contoso.com/inbox

in URL Structure includes PII in the URL which is prohibited in PII parameters

Is your feature request related to a problem? Please describe.
An external API does not always respond successfully. Server errors for example 50x or 429 Too Many Requests may occur. Manually pressing the send button while waiting for a successful response can be tedious.

Describe the solution you'd like
Be able to set the number of retries and the expected/unexpected status codes o

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?

Bug Report

Restify Version

Documentation ( we're using an old version but the current doc. is still wrong )

Node.js Version

N/A

Expected behaviour

The documentation should explain the maxParamLength

Actual behaviour

The maxParamLength server option should be included in the documentation. It's also a little strange that the server throws a 404 not found when a par

As illustrated by https://app.circleci.com/pipelines/github/grpc-ecosystem/grpc-gateway/281/workflows/57fdb518-e3ee-4f16-9a55-0f417732ca80/jobs/7654/steps, one of the integration tests is sometimes failing with the wrong error. We should figure out why this is happening and fix it.

This should be a good issue to get introduced to the codebase. The test is here: https://github.com/grpc-ecosystem

This is a:

• enhancement

• CakePHP Version: any (collections).

Since you have already used psalm and it's templates feature, I would like to suggest you to type all the collections library

Correct the terminology used in code and documentation so that it is consistent with HTTPie and web standards. Examples:

• body parameter -> data field
• operator -> separator

The Go documentation states the following on http.Request.RemoteAddr:

The HTTP server in this package sets RemoteAddr to an "IP:port" address before invoking a handler.

Therefore, you could expect that a code like this is correct:

package main

import (
	"fmt"
	"net"
	"net/http"

	"github.com/go-chi/chi"
	"github.com/go-chi/chi/middleware"
)

func main() {
	r

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?

I was trying to use REST Assured for the first and was going through the documentation to help me but was getting nowhere. I had put in the correct Maven repository and have copied the relevant classes to be imported but was getting nowhere.
After fiddling around for ages, I had discovered that the classes had to be statically imported but since I had directly copied the classes from the wiki, I

The example uses LocalDb as development which is only a valid option on Windows. Using SQLite as development database will work on all platforms.

Describe the feature
I'd like to be able to document multiple different APIs separately in the same Javalin application. I.e. have 3 handlers go to doc A, and have another 3 handlers go to doc B.

Additional context
The purpose of this feature request is API versioning; I'd like to version my API, and have separate docs for each version.

Are there any documentation on how to deploy this to production? right now if you look at the source code, bunch of codes __NEXT_DATA__ I want to see if these codes are gone in production.

has anyone deployed the front-end to digital ocean?

Is there any documentation regarding CORS preflight requests? Seems like these should automatically be configured based on the swagger definition.

I'm looking to return the verbs defined in swagger for my resources (paths) but I can't even find how to control "preFlightContinue" option.

Thanks in advance.

Gitbook will be the new location of documentation

v3 docs will remain on Postman, but will no longer be linked to.

• Write v4 docs
• Move apps list to gitbook
• Move clients list to gitbook

In FAB Security Views we can see some logic related to whitelists.

What we do not see in the Superset or FAB documentation is any mention on how to set them up and what effect they have.

Documentation on this would be useful.

Hello,

I was able to run python scripts in dev mode using the steps provided in documentation. but for production, I am not sure which all folders to keep and the process to follow. editing the local conf and local sh files and running the server_deploy script, I was able to generate the server jar. But still i had to manually add the python context and upload my egg file.
Can someone pleas

• The server SHOULD limit the maximum number of resources to push.
• The depth of the selector SHOULD also be limited by the server.

We need better upgrade instructions for switching from the automatic route generation loader to SF Core routing loader.

One part:
Using the method shortcuts also works when using the symfony core annotation loader as they extend the core Route annotation. So we can keep them in rest-bundle and don't need to deprecate them. The only thing that changes is that it changes the route name as rest-b