The repeater control is a major headache.
In v3.1 the repeaters will be completely rewritten. Control templates are now in JS and can easily be retrieved from the kirki.control.template object.
What this means is that we don't need to define any HTML structure for sub-controls in the repeater control, we can reuse the ones used in the actual controls.
This can also lead to the repeater being extendable, allowing developers to hook their own controls in there - provided of course the controls have the right structure and developers extend the kirki object with the markup for their own controls.
The repeater control is a major headache. In v3.1 the repeaters will be completely rewritten. Control templates are now in JS and can easily be retrieved from the
kirki.control.template
object. What this means is that we don't need to define any HTML structure for sub-controls in the repeater control, we can reuse the ones used in the actual controls.This can also lead to the repeater being extendable, allowing developers to hook their own controls in there - provided of course the controls have the right structure and developers extend the
kirki
object with the markup for their own controls.