Deeper relationship resolving
Changes in: api
We've introduced a new syntax for relationship resolving with the resolve_relations
parameter.
You can now pass the format COMPONENT_NAME.FIELD_NAME
to resolve even nested components, allowing you to create a nested structure with single or multiple choices in repeatable components to be resolved. Before that only the root level fields of your content type where possible to be resolved. The old syntax will continue to work, for future implementation we recommend using the new one.