Voting starts in March for the Drupal Association Board election.
Beta phase evaluation
|Issue category||Bug because the extra nested level in schemas for sequences is arbitrary. You can only define one element. It is a syntax gimmick that makes schema writing harder to understand.|
|Disruption||Disruptive for contributed modules which already include schemas. The change is very easy to make though. There is no sizable work ongoing on core schemas, so no disruption expected for other core patches.|
The config schema definitions for sequences are unnecessary nested and it is confusing in comparison to the mapping element. It is true that in mappings, each element has its own type defined and in sequences this nested list item represents that you define the type/label for the item, but this was found to be confusing because it suggests there may be other item types defined, which is not the case. We can describe the data with a simpler construct.
Remove the nested list level.
User interface changes
Sequences will need to be defined in a simpler way. See https://www.drupal.org/node/2442603 for change notice.