Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
Some plugin types might have a LOT of plugin definitions. Menu links is one exampe but block_content could also provide a lot of potential custom blocks,
which would be too much for the derivative system.
Proposed resolution
One possiblity would be a StoragePluginManagerInterface which adds addDefinition()/updateDefinition()/removeDefinition().
The implementations would have to store this data inside a new database table and retrieve data from there.
Remaining tasks
User interface changes
API changes
Comment | File | Size | Author |
---|---|---|---|
#8 | drupal_2312383_8.patch | 2.07 KB | Xano |
#8 | interdiff.txt | 706 bytes | Xano |
Comments
Comment #1
tim.plunkettComment #2
EclipseGc CreditAttribution: EclipseGc commentedDoes the StaticDiscoveryDecorator not effectively achieve this?
Eclipse
Comment #3
dawehnerNo, this issue is about actually storing the data somewhere.
Comment #4
Wim LeersComment #5
Fabianx CreditAttribution: Fabianx commentedComment #6
XanoData storage is an implementation detail. What happens to the definitions is the manager's problem, not the interface's. Following that logic we could abstract out the methods to a StaticDiscoveryInterface?
Comment #7
Xano@dawehner convinced me of this at DrupalCamp Vienna.
Comment #8
Xano.
Comment #9
XanoThis is really a feature.
Comment #24
smustgrave CreditAttribution: smustgrave at Mobomo commentedWonder after so many years if this is still a valid feature request. If so should we update the issue summary update.