igniteui-angular 21.2.0 → 21.2.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "igniteui-angular",
3
- "version": "21.2.0",
3
+ "version": "21.2.2",
4
4
  "description": "Ignite UI for Angular is a dependency-free Angular toolkit for building modern web apps",
5
5
  "author": "Infragistics",
6
6
  "license": "SEE LICENSE IN LICENSE",
@@ -6,6 +6,29 @@ user-invocable: true
6
6
 
7
7
  # Ignite UI for Angular — UI Components
8
8
 
9
+ ## Prerequisites
10
+ - Angular 20+ project
11
+ - `@angular/cli` installed
12
+ - `igniteui-angular` or `@infragistics/igniteui-angular` added to the project via `ng add igniteui-angular` (or the `@infragistics` variant) or `npm install` — see [Package Variants](#package-variants) below.
13
+ - A theme applied to the application (see [`igniteui-angular-theming`](../igniteui-angular-theming/SKILL.md)).
14
+ - `provideAnimations()` in `app.config.ts` — **required before using any overlay or animated component**
15
+ - The **Ignite UI CLI MCP server** (`igniteui-cli`) is available as a tool provider
16
+
17
+ > **AGENT INSTRUCTION — MCP Server Setup (REQUIRED)**
18
+ >
19
+ > Before using any Ignite UI CLI MCP tools, you MUST verify the MCP server is available
20
+ > by calling `list_components`. If the tool is not available or the call fails,
21
+ > you MUST automatically configure it by following the setup process steps described below.
22
+ >
23
+ > After writing the file, inform the user that the MCP server has been
24
+ > configured and they may need to reload the editor for the tools to activate.
25
+ > Start the MCP server and wait for that MCP server to start before continuing the component-related work.
26
+ > Do NOT skip this step or ask the user to do it manually.
27
+
28
+ ## Setting Up the Ignite UI CLI MCP Server
29
+
30
+ > **Full setup instructions for VS Code, Cursor, Claude Desktop, and JetBrains IDEs are in [`references/mcp-setup.md`](./references/mcp-setup.md).** Read that file for editor-specific configuration steps and verification.
31
+
9
32
  ## MANDATORY AGENT PROTOCOL — YOU MUST FOLLOW THIS BEFORE PRODUCING ANY OUTPUT
10
33
 
11
34
  **This file is a routing hub only. It contains NO code examples and NO API details.**
@@ -41,15 +64,6 @@ Base your code and explanation exclusively on what you read. If the reference fi
41
64
 
42
65
  ---
43
66
 
44
- ## Prerequisites
45
-
46
- - Angular 20+ project
47
- - `@angular/cli` installed
48
- - `igniteui-angular` or `@infragistics/igniteui-angular` added to the project via `ng add igniteui-angular` (or the `@infragistics` variant) or `npm install` — see [Package Variants](#package-variants) below.
49
- - A theme applied to the application (see [`igniteui-angular-theming`](../igniteui-angular-theming/SKILL.md)).
50
- - `provideAnimations()` in `app.config.ts` — **required before using any overlay or animated component**
51
-
52
-
53
67
  ## Package Variants
54
68
 
55
69
  | Package | Install | Who uses it |
@@ -15,6 +15,7 @@
15
15
  ## Overview
16
16
 
17
17
  Ignite UI for Angular Charts provides 65+ chart types for data visualization. Charts are packaged separately in `igniteui-angular-charts` (or `@infragistics/igniteui-angular-charts` for licensed users).
18
+ This reference gives high-level guidance on when to use each chart type, their key features, and common API members. For detailed documentation, call `get_doc` and `get_api_reference` from `igniteui-cli` with the specific chart component or feature you're interested in.
18
19
 
19
20
  ### Chart Component packages
20
21
  - `igniteui-angular-charts` — Category Chart, Financial Chart, Data Chart, and Pie Chart components (NPM)
@@ -16,6 +16,9 @@
16
16
  - [Progress Indicators](#progress-indicators)
17
17
  - [Chat (AI Chat Component)](#chat-ai-chat-component)
18
18
 
19
+ ## Overview
20
+ This reference gives high-level guidance on when to use each data display component, their key features, and common API members. For detailed documentation, call `get_doc` and `get_api_reference` from `igniteui-cli` with the specific component or feature you're interested in.
21
+
19
22
  ## List
20
23
 
21
24
  > **Docs:** [List Component](https://www.infragistics.com/products/ignite-ui-angular/angular/components/list)
@@ -133,9 +136,10 @@ import { IgxBadgeComponent } from 'igniteui-angular/badge';
133
136
 
134
137
  ```html
135
138
  <!-- Image avatar with badge overlay -->
136
- <igx-avatar [src]="user.photo" shape="circle" size="large">
137
- <igx-badge igxAvatarBadge [type]="'success'" [icon]="'check'"></igx-badge>
138
- </igx-avatar>
139
+ <div class="avatar-badge-container">
140
+ <igx-avatar [src]="user.photo" shape="circle" size="large"></igx-avatar>
141
+ <igx-badge [type]="'success'" [icon]="'check'"></igx-badge>
142
+ </div>
139
143
 
140
144
  <!-- Initials avatar -->
141
145
  <igx-avatar initials="JD" shape="circle"></igx-avatar>
@@ -147,8 +151,23 @@ import { IgxBadgeComponent } from 'igniteui-angular/badge';
147
151
  <igx-badge [type]="'error'" [value]="unreadCount"></igx-badge>
148
152
  ```
149
153
 
154
+ ```scss
155
+ // Required styles to position the badge as an overlay on the avatar
156
+ .avatar-badge-container {
157
+ position: relative;
158
+ display: inline-flex;
159
+
160
+ igx-badge {
161
+ position: absolute;
162
+ bottom: 0;
163
+ right: 0;
164
+ transform: translate(25%, 25%);
165
+ }
166
+ }
167
+ ```
168
+
150
169
  Avatar shapes: `'circle'`, `'rounded'`, `'square'`. Sizes: `'small'`, `'medium'`, `'large'`, or custom CSS.
151
- Badge types: `'default'`, `'info'`, `'success'`, `'warning'`, `'error'`.
170
+ Badge types: `'primary'`, `'info'`, `'success'`, `'warning'`, `'error'`.
152
171
 
153
172
  ## Icon
154
173
 
@@ -11,6 +11,9 @@
11
11
  - [Tooltip](#tooltip)
12
12
  - [Drag and Drop](#drag-and-drop)
13
13
 
14
+ ## Overview
15
+ This reference gives high-level guidance on when to use each directive, their key features, and common API members. For detailed documentation, call `get_doc` and `get_api_reference` from `igniteui-cli` with the specific directive or feature you're interested in.
16
+
14
17
  ## Button & Icon Button
15
18
 
16
19
  > **Docs:** [Button Component](https://www.infragistics.com/products/ignite-ui-angular/angular/components/button)
@@ -13,6 +13,9 @@
13
13
  - [Banner](#banner)
14
14
  - [Key Rules](#key-rules)
15
15
 
16
+ ## Overview
17
+ This reference gives high-level guidance on when to use each feedback and overlay component, their key features, and common API members. For detailed documentation, call `get_doc` and `get_api_reference` from `igniteui-cli` with the specific component or feature you're interested in.
18
+
16
19
  ## Dialog
17
20
 
18
21
  > **Docs:** [Dialog Component](https://www.infragistics.com/products/ignite-ui-angular/angular/components/dialog)
@@ -18,6 +18,9 @@
18
18
  - [Reactive Forms Integration](#reactive-forms-integration)
19
19
  - [Key Rules](#key-rules)
20
20
 
21
+ ## Overview
22
+ This reference gives high-level guidance on when to use each form control component, their key features, and common API members. For detailed documentation, call `get_doc` and `get_api_reference` from `igniteui-cli` with the specific component or feature you're interested in.
23
+
21
24
  ## Input Group
22
25
 
23
26
  > **Docs:** [Input Group](https://www.infragistics.com/products/ignite-ui-angular/angular/components/input-group)
@@ -9,6 +9,9 @@
9
9
  - [Dock Manager](#dock-manager)
10
10
  - [Tile Manager](#tile-manager)
11
11
 
12
+ ## Overview
13
+ This reference gives high-level guidance on when to use each layout manager component, their key features, and common API members. For detailed documentation, call `get_doc` and `get_api_reference` from `igniteui-cli` with the specific component or feature you're interested in.
14
+
12
15
  ---
13
16
 
14
17
  ## Layout Manager Directives
@@ -12,6 +12,9 @@
12
12
  - [Splitter](#splitter)
13
13
  - [Navigation Drawer](#navigation-drawer)
14
14
 
15
+ ## Overview
16
+ This reference gives high-level guidance on when to use each layout component, their key features, and common API members. For detailed documentation, call `get_doc` and `get_api_reference` from `igniteui-cli` with the specific component or feature you're interested in.
17
+
15
18
  ## Tabs
16
19
 
17
20
  > **Docs:** [Tabs Component](https://www.infragistics.com/products/ignite-ui-angular/angular/components/tabs)
@@ -0,0 +1,77 @@
1
+ # Setting Up the Ignite UI CLI MCP Server
2
+
3
+ > **Part of the [`igniteui-angular-components`](../SKILL.md) skill hub.**
4
+
5
+ ## Contents
6
+
7
+ - [VS Code](#vs-code)
8
+ - [Cursor](#cursor)
9
+ - [Claude Desktop](#claude-desktop)
10
+ - [WebStorm / JetBrains IDEs](#webstorm--jetbrains-ides)
11
+ - [Verifying the Setup](#verifying-the-setup)
12
+
13
+ The Ignite UI CLI MCP server enables AI assistants to discover Ignite UI components, access component documentation, and support related Ignite UI workflows. It must be configured in your editor before these tools become available.
14
+
15
+ ## VS Code
16
+
17
+ Create or edit `.vscode/mcp.json` in your project:
18
+
19
+ ```json
20
+ {
21
+ "servers": {
22
+ "igniteui-cli": {
23
+ "command": "npx",
24
+ "args": ["-y", "igniteui-cli", "mcp"]
25
+ }
26
+ }
27
+ }
28
+ ```
29
+
30
+ This works whether `igniteui-cli` is installed locally in `node_modules` or needs to be pulled from the npm registry — `npx -y` handles both cases.
31
+
32
+ ## Cursor
33
+
34
+ Create or edit `.cursor/mcp.json`:
35
+
36
+ ```json
37
+ {
38
+ "mcpServers": {
39
+ "igniteui-cli": {
40
+ "command": "npx",
41
+ "args": ["-y", "igniteui-cli", "mcp"]
42
+ }
43
+ }
44
+ }
45
+ ```
46
+
47
+ ## Claude Desktop
48
+
49
+ Edit the Claude Desktop config file:
50
+ - **macOS**: `~/Library/Application Support/Claude/claude_desktop_config.json`
51
+ - **Windows**: `%APPDATA%\Claude\claude_desktop_config.json`
52
+
53
+ ```json
54
+ {
55
+ "mcpServers": {
56
+ "igniteui-cli": {
57
+ "command": "npx",
58
+ "args": ["-y", "igniteui-cli", "mcp"]
59
+ }
60
+ }
61
+ }
62
+ ```
63
+
64
+ ## WebStorm / JetBrains IDEs
65
+
66
+ 1. Go to **Settings → Tools → AI Assistant → MCP Servers**
67
+ 2. Click **+ Add MCP Server**
68
+ 3. Set Command to `npx` and Arguments to `-y igniteui-cli mcp`
69
+ 4. Click OK and restart the AI Assistant
70
+
71
+ ## Verifying the Setup
72
+
73
+ After configuring the MCP server, ask your AI assistant:
74
+
75
+ > "List all available Ignite UI components"
76
+
77
+ If the MCP server is running, the `list_components` tool will return all available components for the detected framework.
@@ -146,7 +146,7 @@ For **every** core Ignite UI component chosen in Steps 3-4, follow this MCP-firs
146
146
  - Resolve each value to a palette token or local semantic CSS variable
147
147
  - Call `create_component_theme("grid", ...)` with only `{ "header-background": "<resolved token>", "content-background": "<resolved token>", "row-hover-background": "<resolved token>" }`
148
148
 
149
- Apply the generated theme blocks inside `::ng-deep` scoped to the component selector as shown in the `create_component_theme` output.
149
+ Apply the generated theme block using `@include tokens(<theme-name>);` as returned by `create_component_theme`.
150
150
 
151
151
  Do not run `create_component_theme` for regions built with custom HTML/CSS only.
152
152
 
@@ -118,24 +118,9 @@ igx-nav-drawer {
118
118
  ```
119
119
 
120
120
  ### Dark theme overrides for `IgxGridComponent`
121
- Grid internals often need explicit dark-theme overrides. Use palette tokens or local semantic CSS variables that map to the design:
121
+ Grid internals often need explicit dark-theme overrides. Use `get_component_design_tokens("grid")` to discover available tokens, then call `create_component_theme` with the tokens that differ from the global theme. Apply the returned theme with the `tokens`:
122
122
  ```scss
123
- :host ::ng-deep igx-grid {
124
- .igx-grid__thead,
125
- .igx-grid__tr {
126
- background: <resolved-surface-token>;
127
- }
128
-
129
- .igx-grid__th,
130
- .igx-grid__td {
131
- color: <resolved-text-token>;
132
- border-color: <resolved-border-token>;
133
- }
134
-
135
- .igx-grid__tbody {
136
- background: <resolved-surface-token>;
137
- }
138
- }
123
+ @include tokens($custom-grid-theme);
139
124
  ```
140
125
 
141
126
  ### Read luminance warnings from theme generation
@@ -29,9 +29,11 @@ type IgxBadgeType = (typeof IgxBadgeType)[keyof typeof IgxBadgeType];
29
29
  *
30
30
  * @example
31
31
  * ```html
32
- * <igx-avatar>
33
- * <igx-badge icon="check" type="success"></igx-badge>
34
- * </igx-avatar>
32
+ * <div class="avatar-badge-container">
33
+ * <igx-avatar icon="person" shape="circle" size="small"></igx-avatar>
34
+ * <igx-badge icon="check" type="success" shape="square"></igx-badge>
35
+ * </div>
36
+ * ```
35
37
  */
36
38
  declare class IgxBadgeComponent {
37
39
  /**