Ignite UI for Angular — Data Grids

Ignite UI CLI MCP Server (required)

Verify the igniteui-cli MCP server before any other step by calling list_components with framework: "angular". If the tool is not available, follow the setup procedure in igniteui-angular-components: configure it yourself with npx -y igniteui-cli ai-config (or ig ai-config), ask the user to reload the editor or agent session and stop, and continue without the server only if the user explicitly asks to.

Required Workflow

This file is a routing hub only. It contains no code examples and no API details. Grid APIs change between releases, so never write component selectors, import paths, method names, or property names from memory — read the relevant reference files first.

1. Identify the grid type. Use the Grid Selection Decision Guide below. If the grid type is not explicitly stated, infer it from context or ask.
2. Identify every task category involved. Map the user's request to one or more rows in the Task → Reference File table below. A single request often spans multiple categories (e.g., remote paging plus editing requires both paging-remote.md and editing.md).
3. Read every identified reference file in full, in a single parallel batch of file reads — even if you believe you already know the answer.
4. Then produce output, based only on what you read. If something is not covered by the reference files, look it up with get_doc/search_docs/search_api from the igniteui-cli MCP server. Never guess — if the MCP server cannot answer it, state explicitly that the detail is unverified.

Task → Reference File