Description
Across the CLI MCP flows for React, Web Components, and Angular, the generated apps use Ignite UI components only partially and still fall back to custom HTML/CSS for many common UI patterns.
This does not appear to be caused by missing components or unclear framework support. In all three cases, suitable Ignite UI components exist for much of the generated UI, but they are not being selected and applied consistently during generation.
As a result, the output is only partially aligned with the expected library usage:
React uses Ignite UI mainly for some obvious components such as grids, while other areas like cards, badges, chips, navigation, lists, and progress-related UI are often hand-built
Web Components uses some igc- components, but many common shell and supporting UI parts are still implemented with plain HTML/CSS
Angular uses Ignite UI for major elements, but supporting UI patterns such as status, alerts, badges, progress indicators, and other non-grid content are still often implemented with custom markup or CSS
The repeated issue across all three frameworks is that the generation flow is not consistently following a component-first approach. Instead of checking whether the library already provides a suitable component for a given UI pattern, it often defaults to custom implementation too early.
Proposed Solution
Update the CLI MCP generation flow so that component selection is done in a component-first way across all supported frameworks.
For each planned UI element:
first check whether an Ignite UI component already exists for that pattern
prefer the framework-specific library component when it is a suitable fit
use custom HTML/CSS only when there is no appropriate library component
This should apply consistently across:
Igr* components for React
igc-* components for Web Components
Igx* components for Angular
The goal is for generated apps to use Ignite UI as the default UI building approach, not only for a few major components like grids.
Description
Across the CLI MCP flows for React, Web Components, and Angular, the generated apps use Ignite UI components only partially and still fall back to custom HTML/CSS for many common UI patterns.
This does not appear to be caused by missing components or unclear framework support. In all three cases, suitable Ignite UI components exist for much of the generated UI, but they are not being selected and applied consistently during generation.
As a result, the output is only partially aligned with the expected library usage:
React uses Ignite UI mainly for some obvious components such as grids, while other areas like cards, badges, chips, navigation, lists, and progress-related UI are often hand-built
Web Components uses some igc- components, but many common shell and supporting UI parts are still implemented with plain HTML/CSS
Angular uses Ignite UI for major elements, but supporting UI patterns such as status, alerts, badges, progress indicators, and other non-grid content are still often implemented with custom markup or CSS
The repeated issue across all three frameworks is that the generation flow is not consistently following a component-first approach. Instead of checking whether the library already provides a suitable component for a given UI pattern, it often defaults to custom implementation too early.
Proposed Solution
Update the CLI MCP generation flow so that component selection is done in a component-first way across all supported frameworks.
For each planned UI element:
first check whether an Ignite UI component already exists for that pattern
prefer the framework-specific library component when it is a suitable fit
use custom HTML/CSS only when there is no appropriate library component
This should apply consistently across:
Igr* components for React
igc-* components for Web Components
Igx* components for Angular
The goal is for generated apps to use Ignite UI as the default UI building approach, not only for a few major components like grids.