Skip to content

Schema depth should be configurableΒ #2685

Open
@hareskoug

Description

@hareskoug

Describe the problem to be solved
Depth of JSON request/response schema appears limited to 8, after which no more details are possible to get and instead Recursive is displayed. The sample view does have a configurable max depth; generatedSamplesMaxDepth, which is somewhat helpful but no documentation is provided in this view.

Describe the solution you'd like
An additional configuration option, e.g. generatedSchemaMaxDepth that would enable parity between the schema and sample view in terms of possible depth.

Describe alternatives you've considered

  • Change hard-coded defaults from 8 to something higher, like 10 or 12. It would likely suffice in my scenario but may have other side-effects, plus it's not consistent with how other max depths are controlled.
  • Control max depth in schema using the same property as controls sample depth. I think that would be misleading as the existing property has Samples in its name and should be limited to the samples view only.

Additional context
An example of such a deep (response) structure is here (The response to /v2alpha/data/model/concepts)

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions