Right now \Drupal\entity_browser\Entity\EntityBrowser::route() collects path from display plugin and adds some sane defaults when creating route object. We should allow display plugins to have more power over how route looks like (requirements, defining admin route, ....).
There are more possible solutions:
- display plugin creates full Route objects and EntityBrowser only overrides some things if needed
- keep Route creation in EntityBrowser and allow display plugin to return more info than just path string
There are probably more options but those two sound the simplest and most obvious ones.
- decide on solution
- code patch
- adapt tests
- review patch
N/A
Might change return value of \Drupal\entity_browser\Plugin\EntityBrowser\Display\DisplayRouterInterface::path() will probably change. Maybe we'll even kill that function and entirely replace it with a new one.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
The change introduces an else condition to create a new Route() object using the route information provided by display plugins, allowing for customization of route defaults, requirements, and options as needed.