Skip to content

Allow a way to bypass DataModel recursion depth check #1424

@tranfong1991

Description

@tranfong1991

Currently, if the depth of a data model path is more than 5, an error is thrown:

Image

I assume this is to make sure the LLM isn't producing deeply nested JSONs. However, there are cases where nested data model is necessary. In my case, my data model depth is 6 because my component is referencing data located in paths like "/ai_insights_1/items/0/sources/0/title". It would be great if we allow a way to bypass this check or define our own max depth.

Metadata

Metadata

Assignees

Labels

Type

No type
No fields configured for issues without a type.

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions