Drupal Association members fund grants that make connections all over the world.
Updated: Comment #31
ContentTranslationControllerInterface::get*Path() methods, which provide the paths to be used when building the UI for a particular entity type, should not be translation specific. AAMOF this is a common need and we should be exploiting a generic API instead of providing a one-off solution.
Rely on the Entity links API introduced into generate entity URLs in a generic fashion. Remove the code implementing the current Content-Translation-specific API, deprecate what cannot be removed yet.
Evaluate what has come up fromand . Propose a solution. Post a patch to implement it. Do reviews, update or write tests, evaluate if documentation or a change notice is needed.
User interface changes
- Removed the
- Deprecated the
menu_base_pathentity key (removal needs to wait for the conversion to the new routing system to be complete).
- Added the
linksentity key definition to the custom block entity type.
- Removed the
getViewPath()methods from the
The get*Path() methods, which provide the paths to be used when building the UI for a particular entity type, should belong to a UI controller or whatever comes up fromand where the same issues we have here are being addressed. AAMOF those methods are not specific to translation and atm we need to inject menu router info in the entity info to be able to generate the translation UI in a generic fashion.
And responded in support in
There was a lot of discussion on the entity listing patch about paths known to the controllers, and the need for getURI if only admin paths are known, etc. I think these are fine to discuss in the mentioned related issues and we can keep refining this without the need for any major rework, making this patch free to use its current ways.