build: share example routes with web components

[spike-rabbit]

What kind of change does this PR introduce? (check one with "x")

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Other... Please describe:

What is the current behavior? (You can also link to an open issue here)

Web-component examples are registered through a separate switch statement and do not share the application route configuration.

What is the new behavior?

Web-component examples load their components from the shared lazy route map. Route paths now follow the component selector convention without the -demo suffix.

Does this PR introduce a breaking change? (check one with "x")

• Yes
• No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...

Other information:

[Copilot]

Pull request overview

Aligns the web-components entrypoint with the Angular app’s shared route configuration so examples are loaded from the same lazy route map and route paths follow the component-selector naming convention (without the -demo suffix).

Changes:

• Switched the main app bootstrap to consume routes from app.routes.ts.
• Added a redirect from the empty path to fluid-row-height and renamed the “10k Rows” route to ten-k-rows.
• Refactored web-components example loading to resolve components from the shared routes map instead of a dedicated switch.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File	Description
src/main.web-components.ts	Builds an example loader map from shared routes and registers web component examples dynamically.
src/main.ts	Updates route import to use ./app/app.routes.
src/app/app.routes.ts	Adds default redirect and renames 10k-rows to ten-k-rows in the route map.
src/app/app.component.html	Updates navigation link to the renamed ten-k-rows route.

Suppressed comments (1)

src/app/app.routes.ts:21

• This renames the example route from 10k-rows to ten-k-rows, which will break existing deep links/bookmarks (and any external references) to #/10k-rows. Consider keeping backward compatibility by adding a redirect route from the old path to the new one.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[fh1ch]

@spike-rabbit nice work here, I like the direction 🙇

Just two points from my end, but the rest looks good 🏓

[fh1ch]

IMO, this change doesn't make much sense. Everything is called 10k-rows (file, title, ...), so why do we suddenly call it ten-k? We should align this here, no hard feelings into which direction.

[fh1ch]

Do we have some sort of linting for this? We don't really test our demo app, meaning errors will only be noticed during runtime/by the reader.

[spike-rabbit]

My plan is to generate this file in the future. I guess this is easier than to lint it?