You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a data model with deep nested blocks and those blocks are used in rich text fields. The SDK stops at level 5 resolving relations however this limit is reached quite soon when a nestable block is used in a rich text field.
For getting things to work in our case we have to overwrite this limit.
As a workaround we are overwrite the Client quite ugly:
Level does not start with the defaul 0 but in our case -2. At the end we have a limit of 6 (-2 up to 4). isStopResolving is declared as private so we could not overwrite it directly.
Expected Behavior
Every relation in our rich text could be resolved.
Either we are able to set this level as parameter for the client
or the private method isStopResolving is made protected so we are able to overwrite it in a child class
Current Behavior
Deep nested relations are not resolved.
Steps to Reproduce
Create some content type with deep nested blocks and try to resolve all relations.
The text was updated successfully, but these errors were encountered:
We have a data model with deep nested blocks and those blocks are used in rich text fields. The SDK stops at level 5 resolving relations however this limit is reached quite soon when a nestable block is used in a rich text field.
For getting things to work in our case we have to overwrite this limit.
As a workaround we are overwrite the Client quite ugly:
Level does not start with the defaul 0 but in our case -2. At the end we have a limit of 6 (-2 up to 4).
isStopResolving is declared as private so we could not overwrite it directly.
Expected Behavior
Every relation in our rich text could be resolved.
Current Behavior
Deep nested relations are not resolved.
Steps to Reproduce
Create some content type with deep nested blocks and try to resolve all relations.
The text was updated successfully, but these errors were encountered: