We want to get rid of the old menu system, we want the new routing system. We cannot ship Drupal 8 with 2 routing systems, so this is critical.
Issues to finish the feature set of the new routing system:
#1793520: Add access control mechanism for new router system
#1845402: Update menu link access checks for new router
#1798214: Upcast request arguments/attributes to full objects
Issues to handle everything from hook_menu() that's not in the router system:
#916388: Convert menu links into entities
#1889790: [Meta] Allow modules to register links for menus, breadcrumbs and tabs (if not with hook_menu)
Conversion issues:
All conversion issues should have this tag.
Comments
Comment #0.0
catchUpdated issue summary.
Comment #1
catchI added the two issues i'm aware of around menu links, also adding WSCCI tag.
Comment #2
cweagansThe blockers for this are still in progress - pretty sure that this should be postponed.
Comment #3
catchNo this is a meta issue to track the various sub-issues, nothing specific has to happen here that would be postponed on them.
Comment #3.0
klausireplaced hook_menu issue
Comment #3.1
catchAdding meta-conversion issue
Comment #3.2
Crell CreditAttribution: Crell commentedAdded link to tagged issues.
Comment #4
webchickI think we can close this now. The only open issue remaining from the summary is #1889790: [Meta] Allow modules to register links for menus, breadcrumbs and tabs (if not with hook_menu) but that's all just DX nice-to-haves, as far as I can tell. The routing parts of hook_menu() are split out into module.routing.yml files, with a 'route_name' pointer in hook_menu() to any menu items that involve UI chrome. #1889790: [Meta] Allow modules to register links for menus, breadcrumbs and tabs (if not with hook_menu) is the issue tracking conversions core-wide, and is already critical.
Comment #5
effulgentsia CreditAttribution: effulgentsia commentedI think the second link in #4 was meant to be #1971384: [META] Convert page callbacks to controllers. Since that's critical, I agree with closing this one.
Comment #6
tim.plunkett#2106709: Remove legacy router backward compatibility layer
Comment #6.0
tim.plunkettRemove old text.