Skip to content

#172 - Prefix all the route names of the bundle with cleverage_ui_process_ - #177

Merged
njoubert-cleverage merged 2 commits into
mainfrom
172
Oct 16, 2026
Merged

njoubert-cleverage merged 2 commits into
mainfrom
172

Conversation

@njoubert-cleverage

@njoubert-cleverage njoubert-cleverage commented Oct 16, 2026 •

Copy link
Copy Markdown
Member

Description

Fixes #172. Prefix: cleverage_ui_process_, as the service ids of the bundle. All the routes of the bundle are renamed, including the dashboard and the routes generated by EasyAdmin, with deprecated aliases for the former names (no BC break in 3.x).

Before (deprecated) After
process cleverage_ui_process (dashboard)
process_<crud>_<action> cleverage_ui_process_<crud>_<action>
process_login cleverage_ui_process_login
process_logout cleverage_ui_process_logout
process_list cleverage_ui_process_list
process_launch cleverage_ui_process_launch
http_process_execute cleverage_ui_process_http_execute
  • The dashboard route name is cleverage_ui_process (the prefix without the trailing _), so that EasyAdmin generates cleverage_ui_process_<crud>_<action> (e.g. cleverage_ui_process_process_execution_index) for the CRUD pages.
  • The new names are used everywhere in the bundle: security configuration added to the security extension, HttpProcessExecutionAuthenticator::supports(), controllers, menu, templates.
  • Former names: deprecated route aliases since 3.3, removed in 4.0, in the new config/routes/deprecated_aliases.yaml (loaded by the documented @CleverAgeUiProcessBundle/config/routes/*.yaml import; YAML because the alias option of #[Route] requires Symfony 7.3). The aliases of the routes generated by EasyAdmin are added by the new internal DeprecatedEasyAdminRouteAliasLoader (routing loader imported by this file): it imports easyadmin.routes only to know the names of the routes of the dashboard of the bundle (dashboardControllerFqcn default; the routes of the application dashboards are ignored) and returns the aliases only. Generating a URL with a former name, and opening a ?routeName=<former name> URL, keep working.
  • Docs: route names and former names (users & security, HTTP API), UPGRADE.md (v3.3); the easyadmin.routes loader generates the routes of every dashboard, so a prefix on the import of the bundle routes also applies to the application dashboards.

Checked in process-bundle-demo (patch applied to the vendor, the demo does not reference these route names):

  • debug:router: 43 cleverage_ui_process* routes, no process* route left; process_process_execution_index is an alias of cleverage_ui_process_process_execution_index;
  • HTTP API: invalid token → 401 (the authenticator compares the route name, cf. GHSA-3f6c-2rqw-2rx3);
  • login → dashboard → executions (200), logs, scheduler, users (200), ?routeName=cleverage_ui_process_list and ?routeName=process_list (200), list and launch links with the new names, logout → login;
  • with prefix: /admin on the import: routes and dashboard prefixed together.

Tests: RouteNamesTest (dashboard, generated routes, explicit routes: new names generate and match, former names generate the same paths with the deprecation), DeprecatedEasyAdminRouteAliasLoaderTest (only the routes of the dashboard of the bundle get an alias), deprecated ?routeName=process_list URL; existing tests updated. With coverage (pcov): no risky test, no new uncovered line.

Requirements

  • Documentation updates
    • Reference
    • Cookbooks
    • Changelog
  • Unit tests

Breaking changes

None: the former route names keep working, with a deprecation (3.3, removal in 4.0). Code comparing the _route request attribute with a former name (matching returns the new name) would be affected.

🤖 Generated with Claude Code

njoubert-cleverage and others added 2 commits October 16, 2026 11:24
- Rename the explicit routes: cleverage_ui_process_login, _logout, _list,
  _launch and _http_execute, used by the bundle (security configuration,
  HTTP authenticator, controllers, menu, templates).
- The former names are deprecated route aliases since 3.3
  (config/routes/deprecated_aliases.yaml, loaded by the documented
  config/routes/*.yaml import), removed in 4.0: generating a URL with them
  and ?routeName=<former name> URLs keep working.
- The dashboard route (process) and the EasyAdmin routes generated from it
  are unchanged: no alias possible for the generated routes, renamed in
  4.0.
- Docs: route names, former names, the easyadmin.routes loader generates
  the routes of every dashboard (a prefix on the import also applies to
  the application dashboards); UPGRADE.md.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
- Dashboard route: cleverage_ui_process (was process), so that the routes
  generated by EasyAdmin for the CRUD pages are
  cleverage_ui_process_<crud>_<action> (were process_<crud>_<action>).
- Their former names are deprecated aliases (3.3, removed in 4.0), added
  by the new internal DeprecatedEasyAdminRouteAliasLoader (routing loader
  imported by config/routes/deprecated_aliases.yaml): it imports the
  easyadmin.routes routes to know the names of the routes of the dashboard
  of the bundle (routes of the other dashboards are ignored), and returns
  the aliases only.
- The functional tests declare the loader (executed when the routes are
  loaded by the first test).
- Docs and UPGRADE.md: dashboard and generated routes.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@njoubert-cleverage njoubert-cleverage changed the title #172 - Prefix the route names of the bundle with cleverage_ui_process_ #172 - Prefix all the route names of the bundle with cleverage_ui_process_ Oct 16, 2026
@njoubert-cleverage
njoubert-cleverage merged commit 4d04b90 into main Oct 16, 2026
25 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Prefix the route names of the bundle

1 participant