Views display extenders should only save enabled extenders

Added the array_filter + test coverage to ensure they get filtered. If you run the test on its own without the change, it fails, showing that the issue exists.

This issue blocks 📌 Add validation constraints to views.settings Postponed I believe. So once this gets sorted, that one get go back to NR.

The 'Test-only changes' confirms this successful fails without the array_filter code change. Ready for review.

So now the filtering happens in two spots right? It still happens in Drupal\views\Views::getEnabledDisplayExtenders()

I would think we would want an update hook here that cleans the existing config and then we can remove the filtering in Drupal\views\Views::getEnabledDisplayExtenders() right? Scope wise it makes more sense to me to do that here than in 📌 Add validation constraints to views.settings Postponed but ¯\_(ツ)_/¯

Fixes are made on on 11.x (our main development branch) first, and are then back ported as needed according to our policies.

Don't have an answer for #7 but can MR be updated to 11.x vs 11.0.x please.

scott_euser → changed the visibility of the branch 3460063-views-display-extenders-filter to hidden.

1. Updated to 11.x
2. Added updated hook + addressed feedback from #7

Thanks!

Added 1 super nitpicky void return directly.

Does appear #7 has been addressed and pipeline is green

Code wise use of array_filter makes sense and doesn't seem to cause any issue.

Note that 🐛 views.settings config object should not be used to cache list of available plugins Active proposes removing this config entirely, is effort better spent over there?

Agreed with #14, normally hesitant to mark an RTBC issue duplicate of one that's needs work, but given this includes an upgrade path and that issue will also need one, better to have one update to maintain than two.