Fix the UX of Entity Reference fields [#2116551]

Problem/Motivation [#1757452] added config entities back into the selection here, after this was deliberately taken out in [#1801304] taken out of the UI since the initial ER pach didn't support config entities. This leads to completely silly lists of possible things to reference like this: Here you have your "90% case" stuff (Content, Users, Files, etc.) buried hopelessly in amongst a bunch of "1% or less case" stuff like "Editor" and "Text format" and "Breakpoint group." This needs to be fixed, because it makes what's already a challenging field to use about 600x more difficult.

No search fields to select when creating an entity reference view

Entity Reference Views

8 - Reference View in Entity Reference field - Drupal Answers

CRM (on-prem) – Entity reference cannot have Id and Key Attributes

Entity Reference Referential Integrity

Solved: Business Unit Specific New Contact Form

Entity Reference Ajax Formatter

No search fields to select when creating an entity reference view

drupal - How can I limit an entity reference selection to a

Prioritize 'add existing' in nested entity creation UX to prevent

Add Entity reference field [#1801304]

Error in Action for missing values

AL0604: The identifier field name could not be found · Issue