The fields themselves are added just like any other fields in the options part of the main config with one exception - the type of the field should be in the following format: repeater:signatureID.
Since the Sections field is primarily for aesthetic grouping, it cannot be used within the Repeater.
Doesn't look like much unless you click the Add new button which will result in the following
Thus pressing the Add new button again and again will generate as many items (a.k.a. 'repeatees') as needed.
Note that although I've specified one field in the configuration above (which is the Editor field) 2 of them are present on the screenshot. The title field is there by default and will show the value in the title bar of the repeatee as soon as you type something in. Repeatees would have been harder to distinguish if they weren't 'labeled'.
Sorting
Single click on the toolbar will toggle the visibility of the item, while click and drag will allow to sort
You can sort 'closed' items or 'open' it doesn't matter.
Temporary hiding
If you hover over or expand a repeatee there's a button group that allows to delete or to temporarily hide it. If you press the Hide button, the repeatee's value will not be included in the return value and the item itself will indicate that it's hidden.
Copying a repeatee
If you press the Copy button, it'll work as expected and will produce an exact copy of the repeatee below it. If the target repeatee is hidden, the resulted copy will be hidden as well.
Reusing a repeater's signature
Since repeaters' signatures are defined in their own config it allows developers to reuse a repeater's signature to create several repeater fields.
E.g. the following configuration
will create two separate repeater fields with identical fields using the same signature
Nested repeaters
You can nest repeaters, make sure that the repeaters' signatures are not nested. Here's an example of a repeater inside a repeater inside a repeater (that's right - 3 levels deep)
Repeaters signatures:
Options:
Note that all 3 different signatures are top level (not nested) but the fields part reference them. Thus creating the needed nesting.
Typed repeaters
A repeater field can repeat values of different types. It has a slightly different config signature that has field-types instead of fields in it. Each field-type should have a unique id, nice title (that will be seen on the front end) and the fields key that has regular options settings. E.g.
Repeaters signatures:
Options:
These settings will produce the following:
Clicking any of the types will produce repeatees of the respective type. Since it's a repeater field you can mix and match repeatees of various types under one option ID.
Kinda nice, huh? :)
Params
Name
Type
Description
type
string
repeater:signatureID. Signature ID should match one from the repeaters config. (required)
id
string
Unique ID that will be used to retrieve the value (required)
tab
string
Specifies in which tab this option will be rendered
title
string
Shows a heading to the left of the field
desc
string
Shows a description text (can have HTML)
Simple signature params
Name
Type
Description
id
string
Unique ID that will be used in the type parameter of the field (required)
Unique ID that will be used in the type parameter of the field (required)
field-types
array
Configurations for each repeatee type, which is an array consisting of the required id, title and fields keys. See an example above. (required)
Return value
Repeater field returns an array of associative arrays where array keys are the signature's fields IDs. The results will not include the hidden repeatees.
A nested sample config above may return something as follows:
Typed repeaters return value
Typed arrays return an array with type and value fields, type is the field type ID you specified in the settings and value is a regular repeater return value.