apexgrid-skill 2.3.0 → 2.3.1

package/README.md

@@ -88,7 +88,6 @@ const cols  = await readFile(referencePath('columns-and-templates.md'), 'utf8');
 - [apex-grid GitHub](https://github.com/apexcharts/apexgrid)
 - [npm: apex-grid](https://www.npmjs.com/package/apex-grid)
 - [Lit framework](https://lit.dev)
-- [igniteui-webcomponents](https://www.npmjs.com/package/igniteui-webcomponents) (transitive dep — installs automatically)
 
 ## License
 

package/SKILL.md

@@ -13,7 +13,7 @@ description: >
   `dataPipelineConfiguration` hooks for server-side data.
 metadata:
   author: ApexCharts
-  version: "2.3.0"
+  version: "2.3.1"
   library_version: "3.5.0"
   category: data-visualization
   tags: [grid, data-grid, table, web-component, lit, apex-grid]
@@ -34,9 +34,11 @@ The grid styles itself out of the box (borders, row separators, sort/filter UI)
 npm install apex-grid lit
 ```
 
-`igniteui-webcomponents` is a regular (transitive) dependency — it installs automatically, and you do **not** import any theme CSS from it.
+That is the whole install. `apex-grid` brings its own runtime dependencies (`lit`, `@lit/context`, `@lit-labs/virtualizer`) and there is **no theme CSS to import** from anywhere.
 
-> Confirmed working versions: `apex-grid@3.0.1`, `lit@^3.0.0`.
+> **Changed in 3.5.0:** earlier versions also pulled in `igniteui-webcomponents` and `igniteui-theming` transitively. Both are gone. The grid never registered an Ignite UI element, so nothing you wrote against the grid is affected, but code that relied on `igc-*` elements being installed as a side effect must now depend on that package directly.
+
+> Confirmed working versions: `apex-grid@3.5.0`, `lit@^3.0.0`.
 
 ### 1.2 Register the element + size the host — `setup()` does both
 
@@ -73,7 +75,7 @@ apex-grid {
 }
 ```
 
-> The deprecated `theme` option (and `igniteui-webcomponents`' `configureTheme()`) does **not** change the grid's appearance — it only forwards to igniteui for apps that embed igniteui components alongside the grid. Omit it; use `--ag-*` variables instead.
+> The deprecated `setup({ theme })` option does **not** change the grid's appearance. It only ever forwarded to Ignite UI's `configureTheme()`, and since 3.5.0 it is inert and warns once. Omit it; use `--ag-*` variables instead.
 
 ### 1.4 Minimal example — a styled, sortable, filterable table
 
@@ -422,7 +424,7 @@ Arrow-key navigation, column resize and column reorder all follow inline order r
 ✅ `setup()` (or `import 'apex-grid/define'`) once at app startup.
 
 ### 3. Importing a theme CSS that no longer exists
-❌ `import 'igniteui-webcomponents/themes/light/bootstrap.css'` + `configureTheme('bootstrap')` — obsolete; does not affect the grid.
+❌ `import 'igniteui-webcomponents/themes/light/bootstrap.css'` + `setup({ theme: 'bootstrap' })` is obsolete; it never affected the grid, and as of 3.5.0 the option is inert and that package is not even installed.
 ✅ Nothing to import — the grid styles itself; retheme via `--ag-*` CSS variables. The only required CSS is a host **height**.
 
 ### 4. Stringified `columns` attribute

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "apexgrid-skill",
-  "version": "2.3.0",
+  "version": "2.3.1",
   "description": "AI coding skill for the apex-grid web component — structured reference docs that help AI assistants (Claude, Cursor, Copilot, etc.) generate correct apex-grid code.",
   "keywords": [
     "apex-grid",

package/references/columns-and-templates.md

@@ -124,13 +124,15 @@ const columns: ColumnConfiguration<User>[] = [
       <input type="checkbox" .checked=${value} disabled />
       <small>${row.name}</small>` },
 
-  // Embedded igniteui-webcomponents control
-  { key: 'avatar',
-    cellTemplate: ({ value }) => html`<igc-avatar shape="circle" .src=${value}></igc-avatar>` },
-
-  // Rating widget tied to data type
-  { key: 'satisfaction', type: 'number',
-    cellTemplate: ({ value }) => html`<igc-rating readonly .value=${value}></igc-rating>` },
+  // Prefer the built-in type over a template where one exists:
+  // `avatar` and `rating` are column types, no template needed.
+  { key: 'avatar', type: 'avatar' },
+  { key: 'satisfaction', type: 'rating' },
+
+  // Any custom element works, but YOU must install and register it:
+  // the grid ships no third-party components (see SKILL.md §1.1).
+  { key: 'status',
+    cellTemplate: ({ value }) => html`<my-status-chip .value=${value}></my-status-chip>` },
 ];
 ```