Voting starts in March for the Drupal Association Board election.
Updated: Comment #16
We need to be able to have dots after the config prefix in config entities. This is used by fields, entity form and display modes extensively. And this works with config schema so I don't think we should be completely removing the 'config_test.dynamic.dotted.default' as this is testing that we support their use case. But the issue with the config_test.dynamic entity type is that it has ids with and without a dot. What the config system can not support is this inconsistency.
- Remove the ability for block machine names to have a dot
- Remove the ability for entity display and form mode machine names to have aditional dots
- Change all usages of the config_test.dynamic entity type to have an id with a dot
I think this might have exposed a bug since being able to add a dot into entity display and form mode machine names seems brittle to me as the dot is used to delimit entity types and bundles in CMI files when the modes are used.
Possibly discuss whether we should introduce some sort of automated validation regex on a config entity's annotation?
User interface changes
None so far.