igniteui-cli 15.8.0 → 15.8.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.
Files changed (38) hide show
  1. package/package.json +4 -4
  2. package/templates/blazor/igb/projects/ai-config/files/skills/igniteui-blazor-components/references/client-scripts.md +7 -7
  3. package/templates/blazor/igb/projects/ai-config/files/skills/igniteui-blazor-components/references/form-controls.md +65 -18
  4. package/templates/blazor/igb/projects/ai-config/files/skills/igniteui-blazor-components/references/setup.md +1 -1
  5. package/templates/blazor/igb/projects/ai-config/files/skills/igniteui-blazor-generate-from-image-design/references/component-mapping.md +5 -5
  6. package/templates/blazor/igb/projects/ai-config/files/skills/igniteui-blazor-generate-from-image-design/references/gotchas.md +23 -4
  7. package/templates/blazor/igb/projects/ai-config/files/skills/igniteui-blazor-grids/references/editing.md +4 -3
  8. package/templates/react/igr-ts/constants.d.ts +1 -1
  9. package/templates/react/igr-ts/constants.js +1 -1
  10. package/templates/webcomponents/igc-ts/constants.d.ts +1 -1
  11. package/templates/webcomponents/igc-ts/constants.js +1 -1
  12. package/templates/webcomponents/igc-ts/projects/_base_with_home/files/package.json +1 -1
  13. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/README.md +15 -15
  14. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-choose-components/SKILL.md +36 -36
  15. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-choose-components/reference/mcp-setup.md +8 -6
  16. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-customize-component-theme/SKILL.md +62 -60
  17. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-customize-component-theme/references/mcp-setup.md +8 -6
  18. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-figma-to-app/SKILL.md +107 -94
  19. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-figma-to-app/references/asset-extraction.md +32 -32
  20. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-figma-to-app/references/design-provenance.md +32 -30
  21. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-figma-to-app/references/design-token-bridge.md +84 -71
  22. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-figma-to-app/references/figma-component-map.md +45 -44
  23. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-figma-to-app/references/figma-exploration.md +57 -51
  24. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-figma-to-app/references/mcp-setup.md +23 -23
  25. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-figma-to-app/references/project-setup.md +28 -26
  26. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-figma-to-app/references/theme-generation.md +45 -35
  27. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-figma-to-app/references/validation-patterns.md +38 -29
  28. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-generate-from-image-design/SKILL.md +63 -63
  29. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-generate-from-image-design/references/component-mapping.md +12 -12
  30. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-generate-from-image-design/references/gotchas.md +24 -24
  31. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-grids/SKILL.md +23 -23
  32. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-integrate-with-framework/SKILL.md +23 -23
  33. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-integrate-with-framework/references/angular.md +10 -10
  34. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-integrate-with-framework/references/react.md +9 -9
  35. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-integrate-with-framework/references/vanilla-js.md +9 -9
  36. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-integrate-with-framework/references/vue.md +11 -11
  37. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-migrate-grid-lite-to-premium/SKILL.md +18 -18
  38. package/templates/webcomponents/igc-ts/projects/ai-config/files/skills/igniteui-wc-optimize-bundle-size/SKILL.md +78 -48
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "igniteui-cli",
3
- "version": "15.8.0",
3
+ "version": "15.8.2",
4
4
  "description": "CLI tool for creating Ignite UI projects",
5
5
  "keywords": [
6
6
  "CLI",
@@ -66,9 +66,9 @@
66
66
  "all": true
67
67
  },
68
68
  "dependencies": {
69
- "@igniteui/angular-templates": "~22.2.1580",
70
- "@igniteui/cli-core": "~15.8.0",
71
- "@igniteui/mcp-server": "~15.8.0",
69
+ "@igniteui/angular-templates": "~22.2.1582",
70
+ "@igniteui/cli-core": "~15.8.2",
71
+ "@igniteui/mcp-server": "~15.8.2",
72
72
  "@inquirer/prompts": "^7.9.0",
73
73
  "chalk": "^5.3.0",
74
74
  "glob": "^11.0.0",
@@ -2,13 +2,13 @@
2
2
 
3
3
  Every component parameter ending in `Script` takes the **name** of a JavaScript function registered on the client, not code. Two kinds exist:
4
4
 
5
- **Package scope.** The `api.js` module ships with `IgniteUI.Blazor.Lite`. The full product (`IgniteUI.Blazor` / `IgniteUI.Blazor.Trial`, grids, charts, Dock Manager) does not ship it yet: register there through the `igRegisterScript(name, fn, shouldCall)` window global, which its `app.bundle.js` script tag installs. Its `shouldCall` defaults to `true`, so pass `false` for handlers and templates.
6
-
7
5
  | Kind | Examples | Function receives | Returns |
8
6
  |---|---|---|---|
9
7
  | Template | `ItemTemplateScript`, `GroupHeaderTemplateScript`, `MessageHeaderScript`, … | a context object | an `html` template result, a string, a primitive — anything lit can render |
10
8
  | Event handler | `ChangeScript`, `ClosingScript`, `FocusScript`, … — one per C# event | the DOM `CustomEvent` | nothing |
11
9
 
10
+ **Package scope.** On `IgniteUI.Blazor.Lite`, register through the `api.js` module below; the `igRegisterScript` / `igRemoveScript` / `igTemplating` window globals no longer exist there. The full product (`IgniteUI.Blazor` / `IgniteUI.Blazor.Trial`, grids, charts, Dock Manager) does not ship `api.js` yet: register there through the `igRegisterScript(name, fn, shouldCall)` window global, which its `app.bundle.js` script tag installs. Its `shouldCall` defaults to `true`, so pass `false` for handlers and templates.
11
+
12
12
  ## Registering
13
13
 
14
14
  ```html
@@ -29,20 +29,20 @@ registerScript('OnDialogClosing', (evt) => {
29
29
  ```
30
30
 
31
31
  - The specifier is relative to the importing script's own URL: `./_content/…` from a script at the wwwroot root, `../_content/…` from a subfolder. A classic script's `import()` resolves it against the document base.
32
- - **Register at the top level of a `type="module"` script, or any time before Blazor starts.** Module scripts run once the page is parsed, while Blazor still has to fetch the component bundle before it can render, so registrations from a page-level module script are in place in time. If a registration ever lands after a component rendered, the library logs a console warning naming the script (late registration is not retried yet). For a hard guarantee, register from the app's own JS initializer (`beforeWebStart`).
33
- - The registered function is the script. For the few parameters that take a *value* rather than a function (e.g. `DataScript`), pass `true` as the third argument (`shouldCall`): the function is then called once when the parameter resolves and its result is used. The deprecated `igRegisterScript` global defaults that argument to `true` instead.
32
+ - **Register at the top level of a `type="module"` script, or any time before Blazor starts.** Module scripts run once the page is parsed, while Blazor still has to fetch the component bundle before it can render, so registrations from a page-level module script are in place in time. If a registration lands after a component rendered, the library applies it as soon as it is registered. For a hard guarantee, register from the app's own JS initializer (`beforeWebStart`).
33
+ - The registered function is the script. For the few parameters that take a *value* rather than a function (e.g. `DataScript`), pass `true` as the third argument (`shouldCall`): the function is then called once when the parameter resolves and its result is used.
34
34
  - Other exports: `removeScript(name)`, and `html` — the lit-html template tag, the same instance the components render with. Typings ship at `_content/IgniteUI.Blazor/api.d.ts`.
35
35
  - From a classic (non-module) script use a dynamic import (no top-level `await` there): `import('./_content/IgniteUI.Blazor/api.js').then(({ registerScript, html }) => { /* register */ });`
36
- - The `igRegisterScript` / `igRemoveScript` / `igTemplating.html` window globals still work with the same signatures once the library has loaded, but are deprecated and warn in the console. A classic script that calls them while the page parses (before Blazor starts) needs the `<script src="_content/IgniteUI.Blazor/app.bundle.js">` tag, which queues those calls until `api.js` loads; without the tag, move the call to a module script.
37
36
 
38
37
  ## Templates
39
38
 
40
39
  A template function receives one context object and returns an `html` template result, a string, a primitive value — anything lit can render. `html` is only needed for markup; plain text can be returned directly, and an empty string renders nothing.
41
40
 
42
- The context mirrors the component's .NET template context: the same data is exposed under the same names — the item for a list item, the message for a chat message — so start from the component's C# template context type when writing one.
41
+ The context mirrors the component's .NET template context: the same data is exposed under the same names — the item for a list item, the message for a chat message — so start from the component's C# template context type when writing one. One exception: a Combo group header gets `{ item }`, a record holding the group's value under the `GroupKey` field, which the C# `IgbComboGroupHeaderContext` of `IgniteUI.Blazor.Lite` exposes as `Key`.
43
42
 
44
43
  ```razor
45
- <IgbCombo T="City" Data="Cities" ValueKey="Id" DisplayKey="Name" GroupKey="Country"
44
+ @* Full product: T="string" in place of TValue and TItem *@
45
+ <IgbCombo TValue="string" TItem="City" Data="Cities" ValueKey="Id" DisplayKey="Name" GroupKey="Country"
46
46
  ItemTemplateScript="CityItem" GroupHeaderTemplateScript="CountryHeader" />
47
47
  ```
48
48
 
@@ -4,6 +4,17 @@ Module for every component below is `Igb<Name>Module` (`IgbInputModule`, `IgbCom
4
4
 
5
5
  Verify exact members with `get_api_reference` / `get_doc` when the MCP server is available — the tables here list the members these controls are normally driven by, not their full API.
6
6
 
7
+ The examples compile in both packages, and the types shown are the full `IgniteUI.Blazor`'s. In `IgniteUI.Blazor.Lite`, Calendar, Color Picker, Date Picker, Date Range Picker, Date Time Input, Radio Group, Rating, Select and Slider are generic over `TValue`, the type of their value; each section lists the types it takes. Razor infers `TValue` from `@bind-Value` or `Value`, but not through a method group, so set it when there is no value, or when a method handles an event that carries the value. Those events carry generic args, such as `IgbNumberEventArgs<TValue>`:
8
+
9
+ ```razor
10
+ <IgbSlider TValue="double" @bind-Value="Volume" Change="OnVolumeChange" />
11
+
12
+ @code {
13
+ double Volume { get; set; } = 40;
14
+ void OnVolumeChange(IgbNumberEventArgs<double> e) => Console.WriteLine(e.Detail);
15
+ }
16
+ ```
17
+
7
18
  ## Text inputs
8
19
 
9
20
  `IgbInput` and `IgbTextarea` share a base: `Label`, `Placeholder`, `Outlined`, `Disabled`, `Required`, `Invalid`, plus `Value` / `ValueChanged`.
@@ -40,27 +51,38 @@ Icons in `prefix` / `suffix` slots must be `IgbIcon`. A `<span class="material-i
40
51
  ## Combo Box
41
52
 
42
53
  ```razor
43
- <IgbCombo T="City" Data="Cities" ValueKey="Id" DisplayKey="Name"
54
+ <IgbCombo Data="Cities" ValueKey="Id" DisplayKey="Name" @bind-Value="SelectedCityIds"
44
55
  Label="Select Cities" Placeholder="Pick a city" />
45
56
 
46
57
  @code {
47
58
  private List<City> Cities = SampleData.Cities;
59
+ private string[] SelectedCityIds = [];
48
60
  record City(string Id, string Name, string Country);
49
61
  }
50
62
  ```
51
63
 
52
- The generic parameter is **`T`**, not `TValue` — set it to the data item type. `IgbCombo` does not participate in a plain HTML `<form>`; bind its value explicitly.
64
+ The combo is generic over its value type: the `ValueKey` property's type (here `City.Id`, `string`), or the item type when there is no `ValueKey`. `Value` is an array of it, even with `SingleSelect`. The full `IgniteUI.Blazor` names it `T`; `IgniteUI.Blazor.Lite` names it `TValue` and adds `TItem`, the item type `Data` takes. Razor infers them from `@bind-Value` and `Data`, so the example sets neither. Set them when there is nothing to infer them from, and in Lite whenever the combo has a `Change` handler, as its args are `IgbComboChangeEventArgs<TValue, TItem>`: `<IgbCombo T="string" …>` in the full product, `<IgbCombo TValue="string" TItem="City" …>` in Lite. `IgbCombo` does not participate in a plain HTML `<form>`; bind its value explicitly.
53
65
 
54
66
  ## Select
55
67
 
56
68
  ```razor
57
- <IgbSelect @bind-Value="Fruit" Label="Fruit" Placeholder="Choose a fruit">
58
- <IgbSelectItem Value="apple">Apple</IgbSelectItem>
59
- <IgbSelectItem Value="orange">Orange</IgbSelectItem>
69
+ <IgbSelect @bind-Value="CountryCode" Label="Country" Placeholder="Choose a country">
70
+ @foreach (var country in Countries)
71
+ {
72
+ <IgbSelectItem Value="@country.Code">@country.Name</IgbSelectItem>
73
+ }
60
74
  </IgbSelect>
75
+
76
+ @code {
77
+ string? CountryCode { get; set; }
78
+ private List<Country> Countries = SampleData.Countries;
79
+ record Country(string Code, string Name);
80
+ }
61
81
  ```
62
82
 
63
- `Value` is `string?`. `Change` carries `IgbSelectItemComponentEventArgs`. `IgbSelectHeader` and `IgbSelectGroup` add section headings and grouping.
83
+ Write item values as C# expressions, `Value="@country.Code"` or `Value="@("us")"`, which works in both packages. Use `Placeholder` for the empty state rather than an empty item. `IgbSelectHeader` and `IgbSelectGroup` add section headings and grouping.
84
+
85
+ In `IgniteUI.Blazor.Lite`, `IgbSelect<TValue>` is generic: it takes `string`, `char`, an enum, or a numeric type, each optionally nullable. Each item infers its own `TValue` from its `Value`, so item values must have the select's exact type: an `int?` select needs `int?` values, not `int`. A bare `Value="apple"` is a C# expression there, reads as the identifier `apple`, and does not compile. `Change` carries `IgbSelectItemComponentEventArgs<TValue>`, whose `Detail` is the selected `IgbSelectItem<TValue>`. In the full product `Value` is a `string`.
64
86
 
65
87
  ## Date and time
66
88
 
@@ -80,13 +102,17 @@ The generic parameter is **`T`**, not `TValue` — set it to the data item type.
80
102
  <IgbDateTimeInput @bind-Value="SelectedDateTime" InputFormat="MM/dd/yyyy HH:mm" SpinLoop="true" />
81
103
 
82
104
  @code {
83
- DateTime? SelectedDate { get; set; } // picker / date-time input are nullable
84
- DateTime CalendarValue { get; set; } = DateTime.Today; // IgbCalendar.Value is non-nullable
105
+ DateTime? SelectedDate { get; set; }
106
+ DateTime? MinDate { get; set; } = DateTime.Today;
107
+ DateTime? MaxDate { get; set; } = DateTime.Today.AddYears(1);
108
+ DateTime CalendarValue { get; set; } = DateTime.Today;
85
109
  DateTime? SelectedDateTime { get; set; } = DateTime.Now;
86
110
  }
87
111
  ```
88
112
 
89
- `IgbCalendar.Value` is a non-nullable `DateTime`; the pickers are nullable. Multi and range calendar selection come from `Selection` (`CalendarSelection.Single | Multiple | Range`).
113
+ In the full product `IgbCalendar.Value` is a non-nullable `DateTime` and the pickers are nullable. Multi and range calendar selection come from `Selection` (`CalendarSelection.Single | Multiple | Range`).
114
+
115
+ In `IgniteUI.Blazor.Lite`, `IgbDatePicker<TValue>`, `IgbDateRangePicker<TValue>`, `IgbCalendar<TValue>` and `IgbDateTimeInput<TValue>` take `DateTime`, `DateTime?`, or `string`, the Date Range Picker's `Value` being an `IgbDateRangeValue<TValue>`; `Min`, `Max` and `ActiveDate` take the same `TValue`, and the Calendar's `Values` is a `TValue[]`. Dates reported back are UTC (`Kind = Utc`), and `string` values come back in round-trip `"o"` form (e.g. `2026-01-02T03:04:05.0000000Z`). A cleared `DateTime?` or `string` is `null`; a cleared `DateTime` is `DateTime.MinValue`.
90
116
 
91
117
  ## Checkbox, Switch, Radio
92
118
 
@@ -97,18 +123,27 @@ The generic parameter is **`T`**, not `TValue` — set it to the data item type.
97
123
  <IgbSwitch @bind-Checked="IsDarkMode">Dark Mode</IgbSwitch>
98
124
 
99
125
  <IgbRadioGroup @bind-Value="Plan" Alignment="ContentOrientation.Vertical">
100
- <IgbRadio Value="basic">Basic</IgbRadio>
101
- <IgbRadio Value="pro">Pro</IgbRadio>
102
- <IgbRadio Value="enterprise">Enterprise</IgbRadio>
126
+ <IgbRadio name="plan" Value="@("basic")">Basic</IgbRadio>
127
+ <IgbRadio name="plan" Value="@("pro")">Pro</IgbRadio>
128
+ <IgbRadio name="plan" Value="@("enterprise")">Enterprise</IgbRadio>
103
129
  </IgbRadioGroup>
104
130
  ```
105
131
 
106
- Radios are grouped by being children of `IgbRadioGroup`, and the selected option is the group's `Value`. Do **not** set `Name` to group them — `Name` is the framework's element identity, not the HTML radio name.
132
+ The selected option is the group's `Value`; radio values are written as for `IgbSelectItem`. The radios are only mutually exclusive when they share a `name`: give every radio in a group the same lowercase `name`, unique to that group, or an unbound group lets each radio stay checked. In the full product, do **not** set `Name` to group them — `Name` is the framework's element identity, not the HTML radio name.
133
+
134
+ In `IgniteUI.Blazor.Lite`, `IgbRadioGroup<TValue>` is generic: it takes `string`, `char`, `bool`, an enum, or a numeric type, each optionally nullable; each radio infers `TValue` from its own `Value`, which must have the group's type, and `Change` carries `IgbRadioChangeEventArgs<TValue>`. `Name` on `IgbRadioGroup` passes the name to each of its radios. An enum binds its members directly:
135
+
136
+ ```razor
137
+ <IgbRadioGroup Name="tier" @bind-Value="Tier">
138
+ <IgbRadio Value="PlanTier.Basic">Basic</IgbRadio>
139
+ <IgbRadio Value="PlanTier.Pro">Pro</IgbRadio>
140
+ </IgbRadioGroup>
141
+ ```
107
142
 
108
143
  ## Slider, Range Slider, Rating
109
144
 
110
145
  ```razor
111
- <IgbSlider @bind-Value="Volume" Min="0" Max="100" Step="5" Change="OnSliderChange" />
146
+ <IgbSlider @bind-Value="Volume" @bind-Value:after="OnVolumeChanged" Min="0" Max="100" Step="5" />
112
147
  <IgbRangeSlider Lower="20" Upper="70" Min="0" Max="100" Change="OnRangeChange" />
113
148
  <IgbRating @bind-Value="StarRating" Max="5" AllowReset="true" />
114
149
 
@@ -116,13 +151,13 @@ Radios are grouped by being children of `IgbRadioGroup`, and the selected option
116
151
  double Volume { get; set; } = 40;
117
152
  double StarRating { get; set; } = 3;
118
153
 
119
- void OnSliderChange(IgbNumberEventArgs e) => Console.WriteLine(e.Detail);
154
+ void OnVolumeChanged() => Console.WriteLine(Volume);
120
155
  void OnRangeChange(IgbRangeSliderValueEventArgs e)
121
156
  => Console.WriteLine($"{e.Detail.Lower}-{e.Detail.Upper}");
122
157
  }
123
158
  ```
124
159
 
125
- `Min`, `Max`, `Step`, `LowerBound`, `UpperBound`, `PrimaryTicks`, `SecondaryTicks`, `DiscreteTrack` and the label/tooltip options come from the shared slider base and apply to both sliders. `IgbRangeSlider` uses `Lower` / `Upper` instead of `Value`. `IgbRating.Value` and `IgbSlider.Value` are `double`.
160
+ `Min`, `Max`, `Step`, `LowerBound`, `UpperBound`, `PrimaryTicks`, `SecondaryTicks`, `DiscreteTrack` and the label/tooltip options come from the shared slider base and apply to both sliders. `IgbRangeSlider` uses `Lower` / `Upper` instead of `Value`. `@bind-Value:after` reacts to a new value without naming the event args, which differ by package: in the full product `IgbRating.Value` and `IgbSlider.Value` are `double` and their events carry `IgbNumberEventArgs`; in `IgniteUI.Blazor.Lite`, `IgbSlider<TValue>` and `IgbRating<TValue>` take `int`, `long`, `short`, `float`, `double`, or `decimal`, and the slider's `Input` / `Change` and the rating's `Change` / `Hover` carry `IgbNumberEventArgs<TValue>`.
126
161
 
127
162
  ## Color Picker
128
163
 
@@ -144,14 +179,26 @@ An HSV canvas with hue and alpha sliders, an editable color string, preset swatc
144
179
 
145
180
  `Input` fires on every color change while `Change` fires on commit and drives `@bind-Value`; `Opening` / `Opened` / `Closing` / `Closed` track the picker surface. `Required`, `Disabled`, `Invalid` plus `CheckValidityAsync()` / `ReportValidityAsync()` / `SetCustomValidityAsync(message)` behave as on the other form controls.
146
181
 
182
+ In `IgniteUI.Blazor.Lite`, `IgbColorPicker<TValue>` takes `string` as well as `System.Drawing.Color`, either nullable, so a `Color?` property binds directly:
183
+
184
+ ```razor
185
+ <IgbColorPicker @bind-Value="Highlight" Label="Highlight" />
186
+
187
+ @code {
188
+ System.Drawing.Color? Highlight { get; set; }
189
+ }
190
+ ```
191
+
192
+ A cleared `string` picker reports `""`; as a `Color`, `null` or `Color.Empty` clears it and a cleared picker reports the same, and in `Hsl` format the color is rounded to whole-number hue, saturation and lightness. `Input` and `Change` carry `IgbColorPickerValueEventArgs<TValue>`, whose `Detail` is the color as `TValue`.
193
+
147
194
  ## Binding and validation
148
195
 
149
196
  ```razor
150
197
  <IgbInput @bind-Value="Model.Name" Label="Name" Required="true" Invalid="@(!IsNameValid)" />
151
198
  <IgbCheckbox @bind-Checked="Model.Agreed">I agree to the terms</IgbCheckbox>
152
199
  <IgbSelect @bind-Value="Model.Country" Label="Country">
153
- <IgbSelectItem Value="us">United States</IgbSelectItem>
154
- <IgbSelectItem Value="uk">United Kingdom</IgbSelectItem>
200
+ <IgbSelectItem Value="@("us")">United States</IgbSelectItem>
201
+ <IgbSelectItem Value="@("uk")">United Kingdom</IgbSelectItem>
155
202
  </IgbSelect>
156
203
  ```
157
204
 
@@ -79,7 +79,7 @@ For `IgniteUI.Blazor.Lite` the theme stylesheet is the only required tag — wit
79
79
  <script src="_framework/blazor.web.js"></script>
80
80
  ```
81
81
 
82
- On the full product, **never wrap that tag in `@Assets[...]`** — fingerprinting it breaks loading and the app renders blank ([#233](https://github.com/IgniteUI/igniteui-blazor/issues/233)). On `IgniteUI.Blazor.Lite`, an existing tag — fingerprinted or not — is a harmless no-op kept for compatibility.
82
+ On the full product, **never wrap that tag in `@Assets[...]`** — fingerprinting it breaks loading and the app renders blank ([#233](https://github.com/IgniteUI/igniteui-blazor/issues/233)). `IgniteUI.Blazor.Lite` no longer ships `app.bundle.js`; remove any existing tag, which would otherwise return 404.
83
83
 
84
84
  Theme files under `_content/IgniteUI.Blazor/themes/` are `{light|dark}/{bootstrap|material|fluent|indigo}.css` — link exactly one.
85
85
 
@@ -57,17 +57,17 @@ Only pick a grid when the content is genuinely tabular. A list of records with r
57
57
  | Text field, search box, inline editor | `IgbInput` | `Label`, `Placeholder`, `Outlined`, `@bind-Value` |
58
58
  | Multi-line text | `IgbTextarea` | `Rows`, `Resize` |
59
59
  | Dropdown selecting a value | `IgbSelect` + `IgbSelectItem` | |
60
- | Searchable / multi-select picker | `IgbCombo` | generic parameter is `T`; `Data`, `DisplayKey`, `ValueKey` |
60
+ | Searchable / multi-select picker | `IgbCombo` | generic over the value type: `TValue` and `TItem` in Lite, `T` in the full product; `Data`, `DisplayKey`, `ValueKey` |
61
61
  | Contextual action menu | `IgbDropdown` | trigger in `slot="target"` — not for form values |
62
- | Date picker | `IgbDatePicker` (`DateTime?`) | |
62
+ | Date picker | `IgbDatePicker` | `DateTime?` in the full product; Lite: `<TValue>` is `DateTime`, `DateTime?` or `string` |
63
63
  | Date range | `IgbDateRangePicker` | |
64
- | Always-visible calendar | `IgbCalendar` (`DateTime`, non-nullable) | `Selection`, `VisibleMonths` |
64
+ | Always-visible calendar | `IgbCalendar` | `Selection`, `VisibleMonths`; non-nullable `DateTime` in the full product, Lite takes `<TValue>` as the date picker does |
65
65
  | Masked entry (phone, postal) | `IgbMaskInput` | `Mask`: `0` digit, `L` letter, `A` alphanumeric |
66
66
  | Checkbox / switch | `IgbCheckbox` / `IgbSwitch` | `@bind-Checked` |
67
- | Radio options | `IgbRadioGroup` + `IgbRadio` | `@bind-Value` on the **group**; do not use `Name` to group |
67
+ | Radio options | `IgbRadioGroup` + `IgbRadio` | `@bind-Value` on the **group**; do not use `Name` to group in the full product (give its radios the same lowercase `name`) |
68
68
  | Slider / range slider | `IgbSlider` / `IgbRangeSlider` | range uses `Lower` / `Upper` |
69
69
  | Star rating | `IgbRating` | |
70
- | Color picker / color swatch input | `IgbColorPicker` | `@bind-Value` (CSS color string), `Mode` (`Default` trigger / `Input` field), `Format`, `ShowAlpha`, `Swatches` |
70
+ | Color picker / color swatch input | `IgbColorPicker` | `@bind-Value` (CSS color string; Lite also `System.Drawing.Color`), `Mode` (`Default` trigger / `Input` field), `Format`, `ShowAlpha`, `Swatches` |
71
71
  | Primary action button | `IgbButton` | `Variant`: `Contained`/`Outlined`/`Flat`/`Fab` |
72
72
  | Segmented / toggle control | `IgbButtonGroup` + `IgbToggleButton` | |
73
73
  | Icon-only button | `IgbIconButton` | |
@@ -29,6 +29,25 @@ Mixing literal text with `@(...)` in one attribute on a component fails the buil
29
29
  @code { void NavigateToDashboard() => NavigationManager.NavigateTo("/dashboard"); }
30
30
  ```
31
31
 
32
+ ### CS0103 — a bare string `Value` on `IgbSelectItem` / `IgbRadio`
33
+
34
+ In `IgniteUI.Blazor.Lite` their `Value` is generic (`TValue`, which must match the parent `IgbSelect` / `IgbRadioGroup`), so the attribute is a C# expression and `Value="apple"` reads as an identifier. Enum members, numbers and loop variables (`Value="Plan.Pro"`, `Value="1"`, `Value="item.Id"`) need no quoting; only a fixed string does.
35
+
36
+ ```razor
37
+ @* ❌ *@ <IgbSelectItem Value="apple">Apple</IgbSelectItem>
38
+ @* ✅ *@ <IgbSelectItem Value="@("apple")">Apple</IgbSelectItem>
39
+ ```
40
+
41
+ ### CS1503 / RZ10001 — `TValue` on a value control's event handler
42
+
43
+ In `IgniteUI.Blazor.Lite` the value controls (Calendar, Color Picker, Date Picker, Date Range Picker, Date Time Input, Radio Group, Rating, Select, Slider) are generic over `TValue`. Razor infers it from `@bind-Value` or `Value`, but not through a method group, so a method handling a value event fails even next to `@bind-Value`, and a control with no value cannot infer it at all. Set `TValue`, or react with `@bind-Value:after`, which works in both packages.
44
+
45
+ ```razor
46
+ @* ❌ *@ <IgbSlider @bind-Value="Volume" Change="OnVolumeChange" />
47
+ @* ✅ *@ <IgbSlider TValue="double" @bind-Value="Volume" Change="OnVolumeChange" />
48
+ @* ✅ *@ <IgbSlider @bind-Value="Volume" @bind-Value:after="OnVolumeChanged" />
49
+ ```
50
+
32
51
  ### BL0005 — setting parameters through `@ref`
33
52
 
34
53
  Assigning component parameters from `OnAfterRenderAsync` (`chart.Brushes = "…"`) raises *"Component parameter should not be set outside of its component"*. Pass them as inline markup attributes instead.
@@ -195,17 +214,17 @@ A font-icon `<span>` is `display: inline`, so `vertical-align` is ignored by the
195
214
 
196
215
  The parameter is `IconName`; `Name` is the framework's element identity on every component. Register the icon in `OnAfterRenderAsync(firstRender)` after `await EnsureReady()`, or nothing renders.
197
216
 
198
- ### `Name` never groups or names a form field
217
+ ### Grouping radios: lowercase `name`
199
218
 
200
- `<IgbRadioGroup Name="plan">` does not group radios — being children of the group does, and the selection is the group's `@bind-Value`.
219
+ Radios are mutually exclusive only when they share an HTML `name`: give every `IgbRadio` in a group the same lowercase `name`, and read the selection from the group's `@bind-Value`. In the full product `Name` is the framework's element identity and does not group them. In `IgniteUI.Blazor.Lite`, `Name` on `IgbRadioGroup` passes the name to its radios.
201
220
 
202
221
  ### `IgbAvatar` uses `Shape`
203
222
 
204
223
  `AvatarShape.Circle | Rounded | Square`. There is no `RoundShape`.
205
224
 
206
- ### `IgbCombo`'s generic parameter is `T`
225
+ ### `IgbCombo`'s generic parameters differ per package
207
226
 
208
- `<IgbCombo T="Person" …>`, not `TValue`.
227
+ `IgniteUI.Blazor.Lite`: `<IgbCombo TValue="int" TItem="Person" …>`. Full `IgniteUI.Blazor`: `<IgbCombo T="int" …>`. `TValue` / `T` is the value type: the `ValueKey` property's type, or the item type without a `ValueKey` — not the item type of a keyed combo. Razor infers them from `@bind-Value` and `Data`, but in Lite a `Change` handler needs both set explicitly.
209
228
 
210
229
  ### `IgbCard` has no default width
211
230
 
@@ -134,10 +134,11 @@ Validate in `CellEdit` / `RowEdit` and set `args.Detail.Valid = false` to block
134
134
  <IgbColumn Field="AssignedTo" Header="Assigned To" Editable="true">
135
135
  <InlineEditorTemplate>
136
136
  @{ var cell = (IgbCellTemplateContext)context; }
137
- <IgbCombo T="Person" Data="people" ValueKey="Id" DisplayKey="Name"
138
- SingleSelect="true" @bind-Value="cell.Cell.EditValue" />
137
+ <IgbCombo T="int" Data="people" ValueKey="Id" DisplayKey="Name" SingleSelect="true"
138
+ Value="@(cell.Cell.EditValue is int id ? new[] { id } : Array.Empty<int>())"
139
+ ValueChanged="@((int[] ids) => cell.Cell.EditValue = ids.FirstOrDefault())" />
139
140
  </InlineEditorTemplate>
140
141
  </IgbColumn>
141
142
  ```
142
143
 
143
- `IgbCombo`'s generic parameter is **`T`**, not `TValue`.
144
+ The grids ship in the full `IgniteUI.Blazor`, whose combo has one generic parameter `T`: the value type, here `Person.Id`'s `int`, or the item type when there is no `ValueKey`. `Value` is a `T[]` even with `SingleSelect`, so convert to and from the cell's `EditValue` instead of binding it directly.
@@ -1,4 +1,4 @@
1
1
  export declare const IGNITEUI_REACT_PACKAGE = "igniteui-react@~19.9.0";
2
- export declare const IGNITEUI_REACT_GRIDS_PACKAGE = "igniteui-react-grids@~19.9.0";
2
+ export declare const IGNITEUI_REACT_GRIDS_PACKAGE = "igniteui-react-grids@~19.10.0";
3
3
  export declare const IGNITEUI_REACT_CHARTS_PACKAGE = "igniteui-react-charts@~19.6.0";
4
4
  export declare const IGNITEUI_REACT_GAUGES_PACKAGE = "igniteui-react-gauges@~19.6.0";
@@ -2,6 +2,6 @@
2
2
  Object.defineProperty(exports, "__esModule", { value: true });
3
3
  exports.IGNITEUI_REACT_GAUGES_PACKAGE = exports.IGNITEUI_REACT_CHARTS_PACKAGE = exports.IGNITEUI_REACT_GRIDS_PACKAGE = exports.IGNITEUI_REACT_PACKAGE = void 0;
4
4
  exports.IGNITEUI_REACT_PACKAGE = "igniteui-react@~19.9.0";
5
- exports.IGNITEUI_REACT_GRIDS_PACKAGE = "igniteui-react-grids@~19.9.0";
5
+ exports.IGNITEUI_REACT_GRIDS_PACKAGE = "igniteui-react-grids@~19.10.0";
6
6
  exports.IGNITEUI_REACT_CHARTS_PACKAGE = "igniteui-react-charts@~19.6.0";
7
7
  exports.IGNITEUI_REACT_GAUGES_PACKAGE = "igniteui-react-gauges@~19.6.0";
@@ -1,6 +1,6 @@
1
1
  export declare const IGNITEUI_WEBCOMPONENTS_CORE_PACKAGE = "igniteui-webcomponents-core@~7.1.0";
2
2
  export declare const IGNITEUI_WEBCOMPONENTS_CHARTS_PACKAGE = "igniteui-webcomponents-charts@~7.1.0";
3
3
  export declare const IGNITEUI_WEBCOMPONENTS_GAUGES_PACKAGE = "igniteui-webcomponents-gauges@~7.1.0";
4
- export declare const IGNITEUI_WEBCOMPONENTS_GRIDS_PACKAGE = "igniteui-webcomponents-grids@~7.2.1";
4
+ export declare const IGNITEUI_WEBCOMPONENTS_GRIDS_PACKAGE = "igniteui-webcomponents-grids@~7.3.2";
5
5
  export declare const IGNITEUI_WEBCOMPONENTS_INPUTS_PACKAGE = "igniteui-webcomponents-inputs@~7.1.0";
6
6
  export declare const IGNITEUI_WEBCOMPONENTS_LAYOUTS_PACKAGE = "igniteui-webcomponents-layouts@~7.1.0";
@@ -4,6 +4,6 @@ exports.IGNITEUI_WEBCOMPONENTS_LAYOUTS_PACKAGE = exports.IGNITEUI_WEBCOMPONENTS_
4
4
  exports.IGNITEUI_WEBCOMPONENTS_CORE_PACKAGE = "igniteui-webcomponents-core@~7.1.0";
5
5
  exports.IGNITEUI_WEBCOMPONENTS_CHARTS_PACKAGE = "igniteui-webcomponents-charts@~7.1.0";
6
6
  exports.IGNITEUI_WEBCOMPONENTS_GAUGES_PACKAGE = "igniteui-webcomponents-gauges@~7.1.0";
7
- exports.IGNITEUI_WEBCOMPONENTS_GRIDS_PACKAGE = "igniteui-webcomponents-grids@~7.2.1";
7
+ exports.IGNITEUI_WEBCOMPONENTS_GRIDS_PACKAGE = "igniteui-webcomponents-grids@~7.3.2";
8
8
  exports.IGNITEUI_WEBCOMPONENTS_INPUTS_PACKAGE = "igniteui-webcomponents-inputs@~7.1.0";
9
9
  exports.IGNITEUI_WEBCOMPONENTS_LAYOUTS_PACKAGE = "igniteui-webcomponents-layouts@~7.1.0";
@@ -19,7 +19,7 @@
19
19
  "igniteui-webcomponents-charts": "~7.1.0",
20
20
  "igniteui-webcomponents-core": "~7.1.0",
21
21
  "igniteui-webcomponents-gauges": "~7.1.0",
22
- "igniteui-webcomponents-grids": "~7.2.1",
22
+ "igniteui-webcomponents-grids": "~7.3.2",
23
23
  "igniteui-webcomponents-inputs": "~7.1.0",
24
24
  "igniteui-webcomponents-layouts": "~7.1.0",
25
25
  "lit": "^3.3.2"
@@ -1,27 +1,27 @@
1
1
  # LLM Agent Skills for End Users
2
2
 
3
- This directory contains skills for GitHub Copilot and other LLM agents to help developers use Ignite UI Web Components effectively in their applications.
3
+ This directory contains skills for GitHub Copilot and other LLM agents. The skills help developers use Ignite UI Web Components in their applications.
4
4
 
5
5
  ## What are Skills?
6
6
 
7
- Skills are structured instructions that help AI agents understand and execute common tasks consistently. Each skill is a self-contained guide that provides step-by-step instructions, code examples, and best practices.
7
+ Skills are structured instructions that help AI agents understand and do common tasks consistently. Each skill is a self-contained guide that gives step-by-step instructions, code examples, and best practices.
8
8
 
9
9
  ## Available Skills
10
10
 
11
11
  | Skill | Description | Use When |
12
12
  | ----------------------------------------------------------- | ---------------------------------------------------------------------------------- | ------------------------------------- |
13
- | [igniteui-wc-choose-components](./igniteui-wc-choose-components/SKILL.md) | Identify the right components for a UI pattern and navigate to official docs/demos | Deciding which components to use |
14
- | [igniteui-wc-integrate-with-framework](./igniteui-wc-integrate-with-framework/SKILL.md) | Integrate components into React, Angular, Vue, or vanilla JS applications | Setting up components in your project |
15
- | [igniteui-wc-customize-component-theme](./igniteui-wc-customize-component-theme/SKILL.md) | Customize styling using CSS custom properties, parts, and theming system | Applying custom brand colors/styles |
16
- | [igniteui-wc-generate-from-image-design](./igniteui-wc-generate-from-image-design/SKILL.md) | Implement a view from a screenshot or mockup using Ignite UI Web Components | Converting a design image into UI |
17
- | [igniteui-wc-figma-to-app](./igniteui-wc-figma-to-app/SKILL.md) | Translate Figma screens from any UI kit (Indigo.Design, third-party, or plain frames) into a working app | Implementing a design from a Figma file |
18
- | [igniteui-wc-optimize-bundle-size](./igniteui-wc-optimize-bundle-size/SKILL.md) | Reduce bundle size by importing only needed components and lazy loading | Optimizing production performance |
19
- | [igniteui-wc-migrate-grid-lite-to-premium](./igniteui-wc-migrate-grid-lite-to-premium/SKILL.md) | Migrate from Grid Lite to the premium Data Grid | Adopting enterprise grid features |
20
- | [igniteui-wc-grids](./igniteui-wc-grids/SKILL.md) | Set up a grid: package choice, theming, Shadow DOM, layout, sorting/filtering | Adding or debugging a grid in an app |
13
+ | [igniteui-wc-choose-components](./igniteui-wc-choose-components/SKILL.md) | Identify the correct components for a UI pattern and find the official docs/demos | Deciding which components to use |
14
+ | [igniteui-wc-integrate-with-framework](./igniteui-wc-integrate-with-framework/SKILL.md) | Integrate components into React, Angular, Vue, or vanilla JS applications | Adding components to your project |
15
+ | [igniteui-wc-customize-component-theme](./igniteui-wc-customize-component-theme/SKILL.md) | Customize styles with CSS custom properties, parts, and the theming system | Applying custom brand colors/styles |
16
+ | [igniteui-wc-generate-from-image-design](./igniteui-wc-generate-from-image-design/SKILL.md) | Implement a view from a screenshot or mockup with Ignite UI Web Components | Converting a design image into UI |
17
+ | [igniteui-wc-figma-to-app](./igniteui-wc-figma-to-app/SKILL.md) | Convert Figma screens from any UI kit (Indigo.Design, third-party, or plain frames) into a working app | Implementing a design from a Figma file |
18
+ | [igniteui-wc-optimize-bundle-size](./igniteui-wc-optimize-bundle-size/SKILL.md) | Import only the necessary components and use lazy loading to reduce bundle size | Optimizing production performance |
19
+ | [igniteui-wc-migrate-grid-lite-to-premium](./igniteui-wc-migrate-grid-lite-to-premium/SKILL.md) | Migrate from Grid Lite to the premium Data Grid | Using enterprise grid features |
20
+ | [igniteui-wc-grids](./igniteui-wc-grids/SKILL.md) | Configure a grid: package choice, theming, Shadow DOM, layout, sorting/filtering | Adding or debugging a grid in an app |
21
21
 
22
22
  ## How to Use
23
23
 
24
- When working with an AI agent like GitHub Copilot, reference skills by name or ask questions naturally:
24
+ With an AI agent such as GitHub Copilot, ask questions in plain language or refer to skills by name:
25
25
 
26
26
  ### Natural Questions
27
27
  - "How do I integrate igniteui-webcomponents with React?"
@@ -44,7 +44,7 @@ Each skill contains:
44
44
 
45
45
  - **Example Usage**: Common questions or scenarios
46
46
  - **When to Use**: Situations where the skill applies
47
- - **Related Skills**: Other relevant skills to explore
47
+ - **Related Skills**: Other relevant skills
48
48
  - **Step-by-Step Instructions**: Detailed guidance with code examples
49
49
  - **Framework-Specific Examples**: React, Angular, Vue, and vanilla JS patterns
50
50
  - **Common Issues & Solutions**: Troubleshooting guidance
@@ -53,9 +53,9 @@ Each skill contains:
53
53
 
54
54
  ## Contributing
55
55
 
56
- If you identify gaps in the skills or have suggestions for improvements:
56
+ If you find gaps in the skills or have suggestions for improvements:
57
57
 
58
- 1. [Open an issue](https://github.com/IgniteUI/igniteui-webcomponents/issues) describing the improvement
58
+ 1. [Open an issue](https://github.com/IgniteUI/igniteui-webcomponents/issues) that describes the improvement
59
59
  2. Submit a pull request with the proposed changes
60
60
 
61
61
  ## Additional Resources
@@ -67,4 +67,4 @@ If you identify gaps in the skills or have suggestions for improvements:
67
67
 
68
68
  ## License
69
69
 
70
- These skills are provided under the same license as the Ignite UI Web Components library. See [LICENSE](../LICENSE) for details.
70
+ These skills use the same license as the Ignite UI Web Components library. See [LICENSE](../LICENSE) for details.