Oliwia Rogala

Addressed by #9511

I can confirm that changing that parameter in settings is fine but it doesn't seem to work in the URL. Indeed, it looks like a new issue. Created a separate...

Adding some thoughts/questions for this PR: The change to `HighlightCode` also makes it so that large example values won't be rendered, here's an example with the default Petstore and very...

There's an issue with getting different default values on loading try it out and on resetting it. After clicking on try it out: After clicking on reset: It seems like...

Here's where we set the error because of which the test fails: https://github.com/swagger-api/swagger-ui/blob/cebccaa8745662d61cdefdbad3646034cd15d4f8/src/core/utils/index.js#L481-L488 Looks like we can't parse `" "`. The same thing happens for OpenAPI 2.0 (without changes in...

Investigating a different issue, I found this https://github.com/swagger-api/swagger-ui/blob/f91ca8237eec4bf92fc6da9e1697810c8f25f1cc/src/core/components/parameters/parameters.jsx#L79-L93 It seems like right now this is an expected behaviour so that we don't override the user's changes if they edited any...

It looks to me like we don't validate parameters at all for `application/json` and `application/xml`. When checking for required fields, we skip the JSON validation: https://github.com/swagger-api/swagger-ui/blob/834fe0a48b0bf0cffa95ba9cab4c6ae86e67f058/src/core/plugins/oas3/selectors.js#L270-L272 If the request content...

There is also an issue with OpenAPI 2.0 - we don't validate required parameters in bodies but we do validate their types. It seems that the issue lies here: https://github.com/swagger-api/swagger-ui/blob/1ce9ce0cda2a55bf3896c0d89706400a83ba1d7e/src/core/utils.js#L488-L494...

Addressed in https://github.com/swagger-api/swagger-ui/pull/9639

Investigating this issue within Swagger Client, I found out that the resolve mechanism executes for a long time due to the complexity of the specification with the nested references. The...