This was discovered while working on 📌 Adopt PluginExists validator in relevant places RTBC .
It turns out that there are a good number of views in core (mostly test views, but some are part of modules' shipped config) that reference invalid handler plugin IDs. Apparently these are converted to supported plugin IDs at runtime (or install time? I'm not really sure), but that still means the config we're shipping is invalid.
At the moment, the only reason tests don't fail is because we are allowing Views config schema to accept invalid plugin IDs, and considering the fallback plugin IDs as valid, just so we don't have to fix all those views in 📌 Adopt PluginExists validator in relevant places RTBC . That work should be done in a separate scope (this issue).
If you remove the allowFallback: true lines from Views' config schema, you'll start to get test failures due to various views using invalid handler plugin IDs.
Remove all of the allowFallback: true lines and fix the views which cause trouble.
Do that, and commit it.
Needs work
11.0 🔥
Last updated
Okay, I got the ball rolling here by fixing (I think) nearly all of the kernel tests. Functional tests are probably still going to fail. But I think what I have already got is a good start for someone else to pick up.