- Issue created by @penyaskito
Right now we are validating that a condition plugin for a Segment is allowed on runtime, but not at the config level.
This could eventually lead to consistence issues in edge-cases.
Add FilteredPluginExistsConstraint constraint:
Currently core's PluginExistsConstraintValidator does $definition = $constraint->pluginManager->getDefinition($plugin_id, FALSE);
This should be a similar validator but using getFilteredDefinitions. For that we need to validate the manager implements FilteredPluginManagerInterface.
The consumer should be another argument for the constraint so instead of:
manager: plugin.manager.block
interface: Drupal\Core\Block\BlockPluginInterface
allowFallback: true
we would use:
PluginExists:
manager: plugin.manager.block
interface: Drupal\Core\Block\BlockPluginInterface
allowFallback: true
consumer: 'xb_personalization'
Here in XB is fine, but wondering if this should be in core tbh.
None.
Active
0.0
Personalization
