- 🇳🇱Netherlands Lendude Amsterdam
Since most of Views is config, 🌱 [meta] Add constraints to all config entity types Active should, one day, provide this I hope
In #2341357: Views entity area config is not deployable and missing dependencies → , we identified the fact that no validation is done on the entity ID configuration field. This problem likely exists in numerous Views plugins. When an invalid value is entered, there is no validation error, and the area is silently empty with no indication of why it's not working.
Only 8 Views plugins implement the validation method, PluginBase::validateOptionsForm(). The related submit handler, submitOptionsForm(), has 13 usages, but since many plugins don't need to explicitly implement the submit method, there are likely many places that the validation method should be added.
PluginBase::validateOptionsForm() in plugins that need input validation.Active
11.0 🔥
Last updated
Related to the Views in Drupal Core initiative.
There is consensus among core maintainers that this is a major issue. Only core committers should add this tag.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Since most of Views is config, 🌱 [meta] Add constraints to all config entity types Active should, one day, provide this I hope