The Ignite UI CLI MCP is a Model Context Protocol (MCP) server that enables AI assistants to scaffold projects, modify existing apps, create and update components, and answer documentation questions for Ignite UI for Angular applications. Connect the Ignite UI CLI MCP to your editor, GitHub repository, or desktop AI client and describe what you want - the assistant uses the CLI tools for you.
+The Ignite UI CLI MCP is a Model Context Protocol (MCP) server that enables AI assistants to scaffold projects, modify existing apps, create and update components, and answer documentation questions for {ProductName} applications. Connect the Ignite UI CLI MCP to your editor, GitHub repository, or desktop AI client and describe what you want - the assistant uses the CLI tools for you.
## Overview -Ignite UI CLI MCP gives AI assistants direct access to Ignite UI CLI project scaffolding, component generation, project modification, and documentation-aware workflows through chat or agent mode. The server works alongside Ignite UI Theming MCP - CLI MCP handles project and component workflows while Theming MCP handles palettes, themes, tokens, and styling. Most teams connect both servers in the same AI client session. +Ignite UI CLI MCP gives AI assistants direct access to Ignite UI CLI project scaffolding, component generation, project modification, and documentation-aware workflows through chat or agent mode. The server works alongside [Ignite UI Theming MCP](./theming-mcp.md). CLI MCP handles project and component workflows while Theming MCP handles palettes, themes, tokens, and styling. Most teams connect both servers in the same AI client session. The recommended setup path is to start with Ignite UI CLI first. That path creates the project, installs the required packages, and writes the initial MCP configuration for VS Code. You can also start from an empty folder and let the assistant create the project through MCP, or connect MCP to a project that already exists. **Example prompts to try once connected:** -> _"Create a new Ignite UI for Angular project in this folder, use the recommended defaults, and add a starter dashboard page with sample data."_ +> _"Create a new {ProductName} project in this folder, use the recommended defaults, and add a starter dashboard page with sample data."_ > _"Add a new grid page to this project, wire it to sample data, and keep the current navigation structure."_ @@ -44,7 +44,7 @@ Before configuring the MCP server, make sure you have: - One of the following starting points: - an empty folder for a new project - a project you created with Ignite UI CLI - - an existing Ignite UI for Angular project you want to continue working on + - an existing {ProductName} project you want to continue working on If you want theming tools in the same client session and `igniteui-theming` is not already available in your project, run: @@ -120,6 +120,8 @@ npx --package igniteui-cli igniteui new Use a direct command when you already know the project settings: + + ```bash ig new my-app --framework=angular --type=igx-ts --template=empty ``` @@ -127,12 +129,44 @@ ig new my-app --framework=angular --type=igx-ts --template=empty Matching `npx` form: ```bash -npx --package igniteui-cli igniteui new my-app --framework=angular --type=igx-ts --template=empty +npx ig new my-app --framework=angular --type=igx-ts --template=empty +``` + + + + + +```bash +ig new my-app --framework=react --type=igr-ts --template=top-nav +``` + +Matching `npx` form: + +```bash +npx ig new my-app --framework=react --template=top-nav ``` + + + + +```bash +ig new my-app --framework=webcomponents --template=side-nav +``` + +Matching `npx` form: + +```bash +npx ig new my-app --framework=webcomponents --template=side-nav +``` + + + In guided mode, Ignite UI CLI prompts for the project name, framework, template, theme, and whether to add a component or complete the setup. In direct mode, you provide the framework and any supported options in the command itself. -For more details about project templates, CLI command options, and component scaffolding commands such as `ig add`, see the Ignite UI CLI documentation for Angular. + +For more details about project templates, CLI command options, and component scaffolding commands such as `ig add`, see the [Ignite UI CLI documentation](../general-cli-overview.md). + ### VS Code @@ -410,12 +444,12 @@ Validate that the JSON uses the `mcpServers` structure and that each local serve ## Additional Resources - [AI-Assisted Development with Ignite UI](./ai-assisted-development-overview.md) -- [Ignite UI for Angular Skills](./skills.md) +- [{ProductName} Skills](./skills.md) - [Ignite UI Theming MCP](./theming-mcp.md) Our community is active and always welcoming to new ideas. -- [Ignite UI for Angular **Forums**](https://www.infragistics.com/community/forums/f/ignite-ui-for-angular) -- [Ignite UI for Angular **GitHub**](https://github.com/IgniteUI/igniteui-angular) \ No newline at end of file +- [{ProductName} **Forums**]({ForumsLink}) +- [{ProductName} **GitHub**]({GithubLink}) \ No newline at end of file diff --git a/doc/en/components/ai/skills.md b/doc/en/components/ai/skills.md index f8ee67384..2a2a24af4 100644 --- a/doc/en/components/ai/skills.md +++ b/doc/en/components/ai/skills.md @@ -4,8 +4,11 @@ _description: Learn how to use Agent Skills to supercharge AI-assisted developme _keywords: {ProductName}, agent skills, ai assisted development, github copilot, cursor, windsurf, claude, gemini cli, junie _license: MIT mentionedTypes: [] +last_updated: "2026-04-24" --- + + # {ProductName} Agent Skills {ProductName} ships with **[Agent Skills](https://agentskills.io/)** - structured knowledge files that teach AI coding assistants (GitHub Copilot, Cursor, Windsurf, Claude, Gemini CLI, JetBrains Junie, etc.) how to work with {ProductName}. These skill files provide context-aware guidance on components, grids, data operations, and theming, enabling your AI assistant to generate accurate, idiomatic code that follows best practices. @@ -24,7 +27,7 @@ The skill files live in the [`skills/`]({GithubLink}/tree/master/skills) directo | Components & Layout | [`skills/igniteui-wc-choose-components/SKILL.md`]({GithubLink}/blob/master/skills/igniteui-wc-choose-components/SKILL.md) | Standalone components, form controls, overlays, layout | | Platform Integration | [`skills/igniteui-wc-integrate-with-framework/SKILL.md`]({GithubLink}/blob/master/skills/igniteui-wc-integrate-with-framework/SKILL.md) | Helps with integrating components to the user's platform of choice | | Theming & Styling | [`skills/igniteui-wc-customize-component-theme/SKILL.md`]({GithubLink}/blob/master/skills/igniteui-wc-customize-component-theme/SKILL.md) | Palettes, typography, elevations, component themes, MCP server | -| Optimization | [`skills/igniteui-wc-optimize-bundle-size/SKILL.md`]({GithubLink}/blob/master/skills/igniteui-wc-optimize-bundle-size/SKILL.md) | Ensuring best practices for tree shaking to optimize bundle size +| Optimization | [`skills/igniteui-wc-optimize-bundle-size/SKILL.md`]({GithubLink}/blob/master/skills/igniteui-wc-optimize-bundle-size/SKILL.md) | Ensuring best practices for tree shaking to optimize bundle size | @@ -34,7 +37,7 @@ The skill files live in the [`skills/`]({GithubLink}/tree/master/skills) directo |:------|:-----|:------------| | Components | [`skills/igniteui-react-components/SKILL.md`]({GithubLink}/blob/master/skills/igniteui-react-components/SKILL.md) | Identify the right components, install, import, and use them - JSX patterns, event handling, refs, forms, TypeScript | | Theming & Styling | [`skills/igniteui-react-customize-theme/SKILL.md`]({GithubLink}/blob/master/skills/igniteui-react-customize-theme/SKILL.md) | Palettes, typography, elevations, component themes, MCP server | -| Optimization | [`skills/igniteui-react-optimize-bundle-size/SKILL.md`]({GithubLink}/blob/master/skills/igniteui-react-optimize-bundle-size/SKILL.md) | Ensuring best practices for tree shaking to optimize bundle size +| Optimization | [`skills/igniteui-react-optimize-bundle-size/SKILL.md`]({GithubLink}/blob/master/skills/igniteui-react-optimize-bundle-size/SKILL.md) | Ensuring best practices for tree shaking to optimize bundle size | @@ -117,7 +120,7 @@ For user-level (global) skills available across all projects, use `~/.agents/ski | Project | `.github/skills/`, `.claude/skills/` | | Personal | `~/.copilot/skills/`, `~/.claude/skills/` (Copilot coding agent and GitHub Copilot CLI only) | -> **Tip:** In [VS Code](https://code.visualstudio.com/docs/copilot/customization/agent-skills), these locations also include the general `.agents/skills/` and `~/.agents/skills/` and you can configure additional skill locations using the `chat.agentSkillsLocations` setting. +> **Tip:** In [VS Code](https://code.visualstudio.com/docs/copilot/customization/agent-skills), these locations also include the general `.agents/skills/` and `~/.agents/skills/` and you can configure additional skill locations using the `chat.agentSkillsLocations` setting. ### Claude @@ -174,7 +177,7 @@ Use one of the options below to download and place the skill files into the appr ### **Option A - Use the Ignite UI CLI** -The `ai-config` command copies skill files from your installed {ProductName} package into `.claude/skills/` and writes the Ignite UI MCP server configuration to `.vscode/mcp.json`. If the files already exist and are up-to-date, the command is a no-op. +The `ai-config` command copies skill files from your installed {ProductName} package into `.claude/skills/` and writes the Ignite UI CLI MCP and Theming MCP server entries to `.vscode/mcp.json`. If the files already exist and are up-to-date, the command is a no-op. @@ -189,16 +192,18 @@ This also registers the `@angular/cli` MCP server in `.vscode/mcp.json` alongsid **Using the Ignite UI CLI:** -### **Option A - Use the Ignite UI CLI** -The `ai-config` command copies skill files from your installed {ProductName} package into `.claude/skills/` and writes the Ignite UI MCP server configuration to `.vscode/mcp.json`. If the files already exist and are up-to-date, the command is a no-op. +```bash +npx igniteui-cli ai-config +``` - - -**Using Angular Schematics:** +If you have the Ignite UI CLI installed globally, use the shorter form: ```bash -ng generate @igniteui/angular-schematics:ai-config +ig ai-config +``` + +### **Option B - Manual Copy from `node_modules`** If {ProductName} is already installed in your project, the skill files are available under `node_modules`. To copy them into your project (e.g. into `.agents/skills/`), run: @@ -361,7 +366,7 @@ Once installed, the skill files are available in the respective location and wil The `skills` CLI is an interactive tool that downloads and installs skills directly into your project. Run the following command in your project root: -```shell +```bash npx skills add IgniteUI/{PackageCommon} ``` @@ -408,7 +413,6 @@ For more information on the Theming MCP, refer to the [Ignite UI Theming MCP](./ - [Ignite UI CLI](../general-cli-overview.md) - - Getting Started with {ProductName} - Angular Schematics & Ignite UI CLI @@ -420,4 +424,4 @@ For more information on the Theming MCP, refer to the [Ignite UI Theming MCP](./ Our community is active and always welcoming to new ideas. - [{ProductName} **Forums**]({ForumsLink}) -- [{ProductName} **GitHub**]({GithubLink}) +- [{ProductName} **GitHub**]({GithubLink}) \ No newline at end of file diff --git a/doc/en/components/ai/theming-mcp.md b/doc/en/components/ai/theming-mcp.md index 19e97c2f0..df5d3654a 100644 --- a/doc/en/components/ai/theming-mcp.md +++ b/doc/en/components/ai/theming-mcp.md @@ -1,24 +1,26 @@ --- -title: {Platform} Theming MCP | Infragistics -_description: {Platform} works with the Ignite UI Theming MCP server that allows you to create custom themes, palettes, typography, and elevations for your {ProductName} applications. Learn how to use the MCP server to generate and apply custom themes that match your brand and design requirements. +title: {Platform} Theming MCP | Infragistics +_description: Use the Ignite UI Theming MCP server to generate {ProductName} palettes, themes, typography, and design token overrides through your AI assistant. _keywords: {ProductName} controls, {Platform} widgets, web widgets, UI widgets, Components Suite, Artificial Intelligence, AI, MCP, Model Context Protocol, Theming, Custom Themes, Palettes, Typography, Elevations _license: MIT mentionedTypes: [] --- + + # Ignite UI Theming MCP -The Ignite UI Theming MCP is a Model Context Protocol (MCP) server that enables AI assistants to generate production-ready theming code for Ignite UI applications. MCP is an open standard that lets AI assistants call specialized tools provided by external servers. Connect the Ignite UI Theming MCP to your editor or desktop AI client and describe what you want — the assistant does the rest.
+The Ignite UI Theming MCP is a Model Context Protocol (MCP) server that enables AI assistants to generate production-ready theming code for Ignite UI applications. MCP is an open standard that lets AI assistants call specialized tools provided by external servers. Connect the Ignite UI Theming MCP to your editor or desktop AI client and describe the theme, palette, or component overrides you want generated.
## Overview -Instead of writing styles by hand, you can describe your theming intent in plain language and let an AI assistant generate the correct code for you. The MCP server gives the AI the knowledge and tools it needs to produce accurate theming code — including palettes with proper shade generation, typography, elevations, component design token overrides, and more. +The Ignite UI Theming MCP server gives AI assistants the knowledge and tools to produce accurate theming code, including palettes with proper shade generation, typography, elevations, component design token overrides, and more. -The server supports all four Ignite UI design systems — **Material**, **Bootstrap**, **Fluent**, and **Indigo** — in both light and dark variants. While this guide focuses on {Platform}, the MCP server also works with all Ignite UI component libraries from Infragistics. The `detect_platform` tool reads your `package.json` and selects the correct import paths and selectors automatically. +The server supports all four Ignite UI design systems (**Material**, **Bootstrap**, **Fluent**, and **Indigo**) in both light and dark variants. While this guide focuses on {Platform}, the MCP server also works with all Ignite UI component libraries from Infragistics. The `detect_platform` tool reads your `package.json` and selects the correct import paths and selectors automatically. -Most tools can produce either **Sass** or **CSS** output. Sass output is the default and integrates with the `igniteui-theming` Sass module. CSS output generates ready-to-use CSS custom properties and can be used **without a local Sass toolchain** — the server compiles it for you. +Most tools can produce either **Sass** or **CSS** output. Sass output is the default and integrates with the `igniteui-theming` Sass module. CSS output generates ready-to-use CSS custom properties and can be used **without a local Sass toolchain** - the server compiles it for you. The Ignite UI Theming MCP works alongside the Ignite UI CLI MCP. In practice, the Theming MCP handles palettes, themes, tokens, typography, elevations, and styling workflows, while the CLI MCP handles project creation, project modification, component workflows, and documentation-oriented tasks. Most teams will want both servers connected in the same AI client. @@ -35,7 +37,7 @@ For a concrete combined workflow after setup, see [Build an App End-to-End with > _"What design tokens are available for the button component? Customize it with my brand purple #8b5cf6."_ -> _"My brand guidelines specify exact hex values for every primary shade — create a custom palette with those explicit values."_ +> _"My brand guidelines specify exact hex values for every primary shade - create a custom palette with those explicit values."_ > _"Make the calendar component use smaller spacing."_ @@ -43,9 +45,9 @@ For a concrete combined workflow after setup, see [Build an App End-to-End with Before configuring the MCP server, make sure you have: -- **Node.js** (v18 or later) installed — this provides the `npx` command used to launch the server. +- **Node.js** (v18 or later) installed. This provides the `npx` command used to launch the server. - A project with an **Ignite UI package** listed as a dependency in `package.json`. -- An **AI client with MCP support** — for example, VS Code with GitHub Copilot, Cursor, Claude Desktop, Claude Code, or a JetBrains IDE with the AI Assistant plugin. +- An **AI client with MCP support** - for example, VS Code with GitHub Copilot, Cursor, Claude Desktop, Claude Code, or a JetBrains IDE with the AI Assistant plugin. If you do not have Ignite UI Theming installed yet, run: @@ -69,7 +71,7 @@ npx -y igniteui-theming igniteui-theming-mcp ### How version resolution works -Because `igniteui-theming` is a dependency of `igniteui-angular`, it is already present in your `node_modules` after `npm install`. When you run the launch command above, `npx` detects the locally installed copy and runs it directly — no network request is made. This means the MCP server version always stays in sync with the rest of your Ignite UI packages. +Because `igniteui-theming` is a dependency of `igniteui-angular`, it is already present in your `node_modules` after `npm install`. When you run the launch command above, `npx` detects the locally installed copy and runs it directly. No network request is made. This means the MCP server version always stays in sync with the rest of your Ignite UI packages. If you run the command outside a project (or before running `npm install`), `npx -y` downloads the **latest** version from npm into a temporary cache instead. The server will still start, but `detect_platform` will return `generic` since there is no `package.json` to inspect. @@ -192,11 +194,11 @@ For any other MCP-compatible client, use the STDIO transport with this launch co npx -y igniteui-theming igniteui-theming-mcp ``` -## Customizing AI Behavior with Project Rules +## Customize AI Behavior with Project Rules This section is optional. It is aimed at teams that want to fine-tune _how_ the AI generates theming code to match their existing codebase conventions. -Editors like VS Code and Cursor let you provide project-level instruction files that shape how the AI behaves. The MCP server already teaches the AI _which tools to call and in what order_ — you do not need to repeat that. Instead, use these instruction files to encode your **project's design decisions, code conventions, and file organization** so the AI produces code that fits your codebase on the first try. +Editors like VS Code and Cursor let you provide project-level instruction files that shape how the AI behaves. The MCP server already teaches the AI _which tools to call and in what order_. You do not need to repeat that. Instead, use these instruction files to encode your **project's design decisions, code conventions, and file organization** so the AI produces code that fits your codebase on the first try. ### VS Code (`.github/copilot-instructions.md`) @@ -204,12 +206,12 @@ Editors like VS Code and Cursor let you provide project-level instruction files ## Theming Conventions ### Sass Code Style -- Use `@use` / `@forward` — never `@import`. +- Use `@use` / `@forward` - never `@import`. - Extract repeated color values into Sass variables (e.g., `$brand-hover: #a78bfa`). - Prefer setting primary design tokens over overriding many dependent tokens. For example, setting `$foreground` on a flat button automatically derives `$hover-background`, `$focus-background`, and `$active-background`. -- Keep component overrides scoped — use the component's default selector +- Keep component overrides scoped - use the component's default selector (e.g., `.igx-button--flat`) unless a narrower scope is needed. ``` @@ -224,12 +226,12 @@ globs: ["**/*.scss", "**/styles/**"] ## Project Theming Rules ### Code conventions -- `@use` / `@forward` only — no `@import`. +- `@use` / `@forward` only - no `@import`. - Extract shared colors into variables; do not repeat hex literals. -- Prefer primary tokens — let dependent tokens derive automatically. +- Prefer primary tokens - let dependent tokens derive automatically. - One component override per file. Name the file after the component. - Comment every override with the design rationale. -- Never hard-code gray shades for text — use palette grays so dark mode works. +- Never hard-code gray shades for text - use palette grays so dark mode works. - For dark mode, only the palette changes. Component overrides stay the same. ``` @@ -238,7 +240,7 @@ globs: ["**/*.scss", "**/styles/**"] ## Available Tools -The MCP server exposes a set of tools that the AI uses automatically based on your prompts. You never need to call them directly — just describe what you want. +The MCP server exposes a set of tools that the AI uses automatically based on your prompts. You never need to call them directly. Just describe what you want. To see the current full list of tools and their parameters at any time, ask your AI assistant: @@ -249,15 +251,15 @@ Here is a brief overview of each tool: | Tool | Description | |------|-------------| | `detect_platform` | Reads `package.json` and identifies whether the project uses Ignite UI for Angular, Web Components, React, or Blazor. Selects the correct import paths and component selectors for all subsequent tools. | -| `create_palette` | Generates a color palette with automatic shade variants (50–900, A100–A700) from your base brand colors. Accepts an `output` parameter (`sass` or `css`) and a `designSystem` to select the schema. | -| `create_custom_palette` | Fine-grained palette creation — specify exact hex values for every shade when automatic generation is not suitable. | +| `create_palette` | Generates a color palette with automatic shade variants (50-900, A100-A700) from your base brand colors. Accepts an `output` parameter (`sass` or `css`) and a `designSystem` to select the schema. | +| `create_custom_palette` | Fine-grained palette creation. Specify exact hex values for every shade when automatic generation is not suitable. | | `create_typography` | Sets up a font family and type scale for a given design system. | -| `create_elevations` | Configures box-shadow elevation levels (0–24) for Material or Indigo design systems. | +| `create_elevations` | Configures box-shadow elevation levels (0-24) for Material or Indigo design systems. | | `create_theme` | One-shot complete theme: palette + typography + elevations, ready to include in your `styles.scss`. Accepts a `designSystem` (`material`, `bootstrap`, `fluent`, or `indigo`) and `variant` (`light` or `dark`). | | `set_size` | Sets `--ig-size` globally or for a specific component (`small`, `medium`, or `large`). | | `set_spacing` | Sets `--ig-spacing` (and optionally inline/block overrides) globally or per component. | | `set_roundness` | Sets `--ig-radius-factor` (0 = square, 1 = fully round) globally or per component. | -| `get_component_design_tokens` | Returns all available design tokens for a component — always call this before `create_component_theme`. | +| `get_component_design_tokens` | Returns all available design tokens for a component. Always call this before `create_component_theme`. | | `create_component_theme` | Generates Sass or CSS to customize a component's tokens (colors, borders, etc.). Accepts a `variant` (`light` or `dark`) to select the correct schema. | | `get_color` | Returns a CSS variable reference for a palette color, e.g. `var(--ig-primary-500)`. Supports optional contrast and opacity parameters. | | `read_resource` | Reads built-in reference resources organized into four categories: platform configs (6), palette/typography/elevation presets (5), color guidance (7), and layout/spacing docs (8). | @@ -270,7 +272,7 @@ Here is a brief overview of each tool: > If your project uses the licensed `@infragistics/igniteui-angular` package, tell the AI so it can set the `licensed` parameter on palette, theme, and component tools. This adjusts the generated import paths accordingly. -## Example Scenarios +## Common Workflows The following scenarios show what you can ask the AI to do once the MCP server is connected. @@ -330,7 +332,7 @@ $my-palette: palette( ### Brand-Exact Color Shades -> _"Our design system specifies exact hex values for all 14 shades of our primary green. I'll paste the values — create a custom palette."_ +> _"Our design system specifies exact hex values for all 14 shades of our primary green. I'll paste the values - create a custom palette."_ The AI will call `create_custom_palette` with `mode: "explicit"` for the primary color and auto-generate the rest. See [Palettes](https://www.infragistics.com/products/ignite-ui-angular/angular/components/themes/sass/palettes) for more detail on shade generation. @@ -342,7 +344,7 @@ The AI will call `get_component_design_tokens` first to discover valid token nam ### Layout Adjustments -> _"The calendar feels bloated — reduce its spacing, and make all components slightly smaller."_ +> _"The calendar feels bloated - reduce its spacing, and make all components slightly smaller."_ The AI will call `set_spacing` scoped to the calendar component and `set_size` at the `:root` level. @@ -369,7 +371,7 @@ Ensure `igniteui-angular` and `igniteui-theming` are installed: ng add igniteui-angular ``` -Also confirm that `core()` is called before any other theming mixin in your `styles.scss`. See [Theming with Sass]() for the correct file setup. +Also confirm that `core()` is called before any other theming mixin in your `styles.scss`. See [Theming with Sass](https://www.infragistics.com/products/ignite-ui-angular/angular/components/themes/sass/index) for the correct file setup. ## Additional Resources @@ -399,5 +401,4 @@ Also confirm that `core()` is called before any other theming mixin in your `sty Our community is active and always welcoming to new ideas. - [{ProductName} **Forums**]({ForumsLink}) -- [{ProductName} **GitHub**]({GithubLink}) - +- [{ProductName} **GitHub**]({GithubLink}) \ No newline at end of file diff --git a/doc/en/components/general-cli-overview.md b/doc/en/components/general-cli-overview.md index 2f3b92a11..7a27e22a9 100644 --- a/doc/en/components/general-cli-overview.md +++ b/doc/en/components/general-cli-overview.md @@ -249,7 +249,7 @@ If you have the CLI installed globally: ig ai-config ``` -This copies {ProductName} Agent Skills into `.claude/skills/` and rites the full Ignite UI MCP server configuration, including the CLI and Theming servers, to `.vscode/mcp.json`. If the files already exist and are up-to-date, the command is a no-op. For AI clients other than VS Code, use the manual configuration below. +This copies {ProductName} Agent Skills into `.claude/skills/` and writes the full Ignite UI MCP server configuration, including the CLI and Theming servers, to `.vscode/mcp.json`. If the files already exist and are up-to-date, the command is a no-op. For AI clients other than VS Code, use the manual configuration below. For full setup instructions across all AI clients and Agent Skills wiring, see [Agent Skills](./ai/skills.md) and [Ignite UI CLI MCP](./ai/cli-mcp.md). diff --git a/stats/docStats-Angular.json b/stats/docStats-Angular.json index 42c3ee357..cd0520c35 100644 --- a/stats/docStats-Angular.json +++ b/stats/docStats-Angular.json @@ -764,7 +764,7 @@ "https://staging.infragistics.com/products/ignite-ui-angular/angular/components/geo-map-type-shape-polyline-series" ] }, - "topicsCount": 103, + "topicsCount": 104, "topicsHost": "https://staging.infragistics.com/products/ignite-ui-angular/angular/components", "topicsNote": "the 'topicsWithSamples' provides lookup of topics that used at least 1 sample", "topicsWithSamples": {