Use the new 'entity_reference' Views filter in EntityViewsData::processViewsDataForEntityReference()

Bot is happy and green. I guess this is a new feature. 😅

I'm probably forgetting something about how this could break things for existing sites with existing views config. Especially while 🐛 Views handler loading should respect configuration Active is unresolved. But it's here for folks that want to try it out. Maybe I'm over-thinking it, and this is harmless for legacy sites.

'Oversight' is not entirely fair :)

In ✨ Continuation Add Views EntityReference filter to be available for all entity reference fields Active :

• #110 - This change was suggested by @catch
• #206/#207 - Breaking change flagged/explained a bit more because numeric allows more than entity reference, and valid things potentially

While those messages are just summaries of slack, we had a lot of discussion with @catch about it it and getting Entity Reference filter in without being used was agred to be the only realistic way to not have a breaking change for existing sites, so we had agreed to deal with the opt-in separately in follow-ups. The main candidate for follow-up was suggested to use 🐛 Views handler loading should respect configuration Active so that existing sites using numeric would respect the configuration and not automatically get swapped to entity_reference, but that turns out to be a big can of worms and ended up getting reverted.

For others stumbling across this issue, for now more sites are using https://www.drupal.org/project/views_core_entity_reference → to opt-in to it, or you can opt-in easily yourself as described on that module homepage.

yes, we IMHO need to restart 🐛 Views handler loading should respect configuration Active , the approach I suggested would give us a way to respect the config but in a constrained way (use the plugin in config, but only if it is in a list of supported plugins. Then we can add numeric and entity reference here and existing sites will continue with what they have and new sites will default to entity reference. and then issues to pick the plugin based on the list of allowed types in the UI as well as being able to deprecate some.

Re: #5: hah, fair enough. 😅 Apologies for my less-than-tactful wording, and thanks for not taking it personally!