Last updated
Last updated
Alpha Feature
object-repeat
is currently in alpha status. There are some known issues:
Performance is slow, especially when used with OnlineDB.
Nesting object-repeat
inside another object-repeat
does not work as expected.
It is not possible to use an advanced query
inside a nested object-table
or object-list
(e.g. sorting, or anything other than a direct has-many
relationship on the object).
Issues that have been fixed:
The data inside the object-repeat
does not always reload properly when changed (e.g. after a sync). This was fixed in version 4.27 of the JourneyApps Container.
object-repeat
creates a new “virtual scope” used for nested components. This specifically includes the current object, under the name specified in the as
attribute. This is relevant for:
Shorthand expressions.
Parameters passed to JS functions.
Most components are allowed to be nested, with some specific exceptions:
columns/column
sidebar
Please note:
Nested object-repeat
s are allowed, but do not currently function correctly.
Due to its complexity, object-repeat
does not offer the same performance and speed than object-list
and object-table
. Therefore, it is recommended to keep the number of objects in your collection < 20, and never more than around 50.
object-repeat
is currently very slow when used with OnlineDB
- the user will see items loading one by one. As a workaround, always use object-repeat
with an array
and not a query
when using OnlineDB
.
query
The collection to loop over.
(The same as, e.g., object-table
)
A view variable of type query:
or array:
as
variable name to be used for the repeating object