Voting starts in March for the Drupal Association Board election.
I made a config entity module for the Examples project which was as simple as I could possibly make it:.
Having done that, it seems to me that the amount of code needed to define a config entity could do to be reduced. I think a lot of contrib modules are going to be using config entities, as they make the most sense to use as soon as you have any kind of list of things the user can add to. (Eg: flag, simplenews, nodequeue, context, and so on.)
From what I've found so far, it seems that a lot of them will be repeating code, and using a lot of code to accomplish minor things.
Some things that have stood out when working on the example module:
- you need to subclass EntityAccessController when all you probably want to say is that you have a permission 'administer foobar config' for all operations on the entities
- you need to subclass ConfigEntityListController even if you only want a list of entities that has the label and status.
Both of these could be eased by the addition of controller classes aimed at this use case.
PASSED: [[SimpleTest]]: [MySQL] 58,847 pass(es). View
PASSED: [[SimpleTest]]: [MySQL] 59,415 pass(es). View
FAILED: [[SimpleTest]]: [MySQL] Setup environment: Test cancelled by admin prior to completion. View
PASSED: [[SimpleTest]]: [MySQL] 59,418 pass(es). View
PASSED: [[SimpleTest]]: [MySQL] 59,252 pass(es). View