- π¬π§United Kingdom andrewbelcher
I would actually describe this as a bug, and a have upped it to major as there is no reasonable workaround that I can see.
When validating contexts using the ContextAwarePluginTrait
you get back a list of violations. However, the violations do not have paths set on them, making them very unhelpful, and making reporting back any errors very unhelpful.
With a context aware plugin, set a value that violates a constraint, then call $this->validateContexts()
. You will get violations, but with no paths.
The @todo
suggests using the Symfony Validator will resolve this:
// @todo Implement the Symfony Validator component to let the validator
// traverse and set property paths accordingly.
// See https://www.drupal.org/project/drupal/issues/3153847.
The lingering @todo
in ContextAwarePluginTrait::validateContexts
was found without a corresponding issue while working on
#2273381: Convert ContextAwarePluginBase to traits β
.
Creating a placeholder issue for this since I have no idea what the original problem or intent was; maybe someone can figure this out after the parent issue is resolved.
Postponed
11.0 π₯
plugin system
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
I would actually describe this as a bug, and a have upped it to major as there is no reasonable workaround that I can see.