feat(routing): configure after migration to standalone#59
Conversation
There was a problem hiding this comment.
Pull Request Overview
This PR adds routing configuration support to standalone Angular components after migration from module-based architecture. It replaces the previous boolean router flag with a more comprehensive RoutesConfig interface that supports configurable routing paths.
- Introduced
RoutesConfiginterface withrouterboolean androutesImportPathstring properties - Updated template generation to conditionally import and use
RouterOutletbased on routing configuration - Modified app config generation to import routes from specified path when routing is enabled
Reviewed Changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| src/templates/app.component.ts.template | Added conditional RouterOutlet import and component registration |
| src/public.ts | Replaced boolean router flag with RoutesConfig interface |
| src/generators/SampleAssetsGenerator.ts | Updated routing logic to use new RoutesConfig structure |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
There was a problem hiding this comment.
Pull Request Overview
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
e9713c8 to
0a2da67
Compare
There was a problem hiding this comment.
Pull Request Overview
Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
Closes 3623
Adds minimal configuration needed to add routes to samples after the migration to standalone components.
Related igniteui-angular-samples PR here