In 'focused' view, components still show up all on one page, causes hang

[jarohen]

Hey there :wave:

I've got a decent amount of components in my schema (~75), some of which are mutually recursive (no problem with the recursive rendering btw, works great :slightly_smiling_face:). Trouble is, when I select one component in the menu on the left, the UI hangs for ~10s trying to render them all.

Any way I can get these rendering one-to-a-page in 'focused' view? It seems like the operations go from all-on-one-page to one-to-a-page when I change the render mode from 'read' to 'focused', but the components don't?

Cheers!

James

[wparad]

I'm curious do other tools on https://openapi.tools/ also hang with your spec?

[jarohen]

Hey @wparad, I'll take a look :eyes:

It's an open-source spec, if that helps

James

[jarohen]

Other ones we've already tried:

• redoc has no plans to support it
• swagger-ui seems to barf on any recursive schemas

[jarohen]

Elements from that list looks like it does the job for us - cheers for the pointer! :pray:

[mrin9]

there are few ways you may address the issue. The goal is to reduce the DOM creation on the browser for that you can use the following

• Use focused mode , it creates the least amount of DOM elements on the browser
• If you have large nested schemas use schema-expand-level=1 this will do a lazy creation of DOM elements as an when you expand the schema tree

RapiDoc will dereference the OpenAPI spec if it contains refs inside it. but if you are dealing with a large spec. I would suggest

• dereference it before sending it to RapiDoc using a dereferencing tool
• if your spec is in yaml convert it to JSON before sending it to RapiDoc

These will save some vital processing time on browser

RapiDoc do allow these operations to happen on the server-side so that the browser's performance is not affected. however then we aren't talking abt a free offering.