A $ref containing a link causes "Maximum call stack size exceeded"

[mary-ehlers]

Context

This bug can be reproduced with the following simple OpenAPI spec:

---
openapi: 3.1.0
info:
  title: blah blah
  version: 29
paths:
  /api:
    get:
      responses:
        '200':
          description: success
          content:
            application/json:
              schema:
                type: object
                $ref: https://spec.openapis.org/oas/3.1/schema-base/latest

Attempting to render the above with the HTML suggested here fails with the following console messages:

web-components.min.js:2 Could bundle: Maximum call stack size exceeded
(anonymous)                 @web-components.min.js:2
Promise.catch (async)	
(anonymous)                 @web-components.min.js:2
as                          @web-components.min.js:2
El                          @web-components.min.js:2
t.unstable_runWithPriority  @web-components.min.js:2
qo                          @web-components.min.js:2
bl                          @web-components.min.js:2
(anonymous)                 @web-components.min.js:2
M                           @web-components.min.js:2
x.port1.onmessage           @web-components.min.js:2

By removing the last line of the API spec, it renders fine, so the problem would appear to be specifically in the line

$ref: https://spec.openapis.org/oas/3.1/schema-base/latest

Environment

• Version used: Whatever is live today, Dec 15, 2022
• Environment name and version (e.g. Chrome 39, node.js 5.4): Chrome 108.0.5359.94
• Operating System and version (desktop or mobile): Ubuntu 20.04

[tgalopin]

I have the same issue with local references:

"200": {
    "description": "The address details",
    "content": {
        "application\/json": {
            "schema": {
                "$ref": "#\/components\/schemas\/App_Application_Transformer_Address_AddressTransformer"
            }
        }
    }
}

[blanquer]

I believe this is due to: stoplightio/json-schema-tree#19 (which doesn't seem to have traction)

I've tried to get a schema that crashes elements like that, then manually delete the overriden "description"s of from those schemas from the JSON file, and observed that after doing that, it the stack crash disappears and the document can be rendered without an issue.

I would love for this to be solved as well as this makes it unusable for us, despite the schemas being perfectly fine.