"@list2:iteration._childComponents.get(0).text.value bindings on the target side of a binding isn't working as it should as @list2:iteration._childComponents gets set

[marchant]

In the branch bugfix/iteration-target-binding, repetition.mod's teach has an example, Main's list2, where the left binding shows how to expose a first stab at exposing a default template component, so its properties can be bound where it's being used.

That binding is:

                "@list2:iteration._childComponents.get(0).text.value": {"<-": "@list2:iteration.object", "trace": true}

_childComponents will needs to be renamed to just "components", which exposes them in order, in an array. We should also consider exposing them by name, like:

                "@list2:iteration.components.text.value": {"<-": "@list2:iteration.object", "trace": true}

But before we get to this, this binding has to work. Right now, when @LIST2:iteration._childComponents gets set, the rest of the expression isn't properly evaluated as it should.

This is needs to be fixed to enable the ability to have useable default template components.