alloutflo opened a new pull request, #270:
URL: https://github.com/apache/fineract-backoffice-ui/pull/270

   ## What and why
   
   Redirect the bare `/calendars` and `/meetings` feature roots to 
`/dashboard`, matching the application's existing fallback behavior. Those 
lazy-loaded route trees previously had no empty-path child, so both URLs 
matched the feature prefix but left the outlet blank instead of reaching the 
global wildcard redirect.
   
   The existing entity-scoped list, create, and edit routes are unchanged.
   
   Closes #264
   
   ## Verification
   
   - Focused route specs: 2 passed
   - Full Karma suite: 812 passed
   - Exercised both redirects with Angular Router 22.0.7 against the real 
feature route arrays; all six existing list, create, and edit paths retained 
their URLs
   - `npm run lint`
   - HTML ESLint
   - `npm run format:check`
   - `npm run i18n:check`
   - `npm run check:icons`
   - `npm run build`
   - API client regeneration and drift check
   - ASF license-header check
   - Production dependency license check
   - `npm audit --audit-level=high --omit=dev` (0 vulnerabilities)
   
   `npm run api:surface` still reports the same three pre-existing manifest 
gaps reproduced on clean `main` at `4c884831`; this change does not touch the 
generated API or its surface manifest.
   
   ## Screenshots
   
   Not applicable. This is a route-configuration fix with no visual change.
   
   ## Checklist
   
   - [x] I did not hand-edit generated files under `src/app/api/`.
   - [x] Not applicable: no component or service code was added.
   - [x] Not applicable: no user-facing strings were added.
   - [x] I added regression coverage for both feature roots.
   - [x] Not applicable: no Fineract backend interaction changed; Angular 
Router recognition was verified directly.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to