SvGrid

Reviewed 23h ago.

• tools: 6 tools scanned
• metadata: scanned
• packages: 1 checked

No findings.

Tools (6)

• search

  Ranked full-text search across the SvGrid documentation and demo catalogue. Returns the best pages first with an excerpt and an id you pass to `fetch`. Use this before writing SvGrid code so the API names come from the docs rather than from memory.

• fetch

  Return the full text behind a search result. Pass a doc slug ("help/columns/column-definitions") or a demo id prefixed with "demo:" ("demo:11-stock-market").

• list_examples

  Browse the SvGrid demo catalogue: id, title, category and a one-line blurb. Call with no arguments for the category index, then filter with `query` or `category`, then read one with get_example_source.

• get_example_source

  Return the full .svelte source of one demo by id (e.g. "11-stock-market") - working code to copy, not a summary of it.

• get_api_reference

  The SvGrid public API grouped by category (components, headless, scheduler, data ops, export, row models, features, virtualization, accessibility, utilities), for the version this server tracks.

• check_svgrid_code

  Verify SvGrid code BEFORE handing it to the user. Checks the source against the real exported surface of the current version - <SvGrid> prop names, ColumnDef keys, grid API methods, importable symbols and theme files - plus Svelte 5 runes rules, and returns line-numbered diagnostics with the exact replacement for each. Run it on every file you write that uses SvGrid, fix what it reports, and run it again.