swagger-api / swagger-api/swagger-ui

Swagger-UI Rendering Issue - [Maximum call stack size exceeded]

Open
#9,307 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
29k
Forks
9.3k
Avg merge
2d 23h
Merged PRs (30d)
25

Description

Q&A (please complete the following information)
  • OS: Windows
  • Browser: Chrome
  • Version: org.springdoc:springdoc-openapi-ui:1.7.0
  • Method of installation: Gradle Artifactory
  • Swagger-UI version: 1.7.0
  • Swagger/OpenAPI version: org.springdoc:springdoc-openapi-ui:1.7.0

Swagger/OpenAPI definition:
NONE-NA

Swagger-UI configuration options:
NONE-NA

How can we help?

My POJO for Response is a big object and when I try to hit a GET or a POST request I see swagger-ui rendering errors like below :

RangeError: Maximum call stack size exceeded

something similar to what is mentioned here and here.

I am on JDK 11 and SpringBoot 2.7.13, so I can't use openAPI 3, I have to stick with above versions.
What do you advise here please?

### Quick Note - The response object is too large with a lot of hierarchies.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The report names no repository files, tests, or reproducible OpenAPI definition. Start by reviewing the linked Swagger UI issue and reproducing the failure with a minimal specification representing the large hierarchical response; done means establishing whether the behavior is actionable in Swagger UI or a limitation of the supplied response model.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, javascript, spring-boot
Domain
api, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.