Recipes
Feature pages tell you what each option does. Recipes answer the other question: “how do I build this?” Each one starts from a concrete goal and ends with runnable code and the failure modes we know about.
Recipe shape
Section titled “Recipe shape”Every page follows the same four steps, so you can skim straight to the part you need:
- Problem — the concrete thing you’re building.
- What you need — which grid features to enable, plus any external library and its approximate size.
- Code — runnable code against public, versioned API.
- Caveats — the failure modes we know about.
Recipes are written in vanilla TypeScript. gridConfig is byte-identical across React, Vue, and Angular, so the only thing that changes per framework is how you hand the config to the component and how you bind events — see Framework Adapters and Listening to Events.
Using the grid
Section titled “Using the grid”Built entirely from @toolbox-web/grid — supported, versioned, and covered by our tests.
Integrating a third-party library
Section titled “Integrating a third-party library”These reach a capability the grid deliberately does not ship. The grid holds a hard bundle budget — core stays under 50 kB gzipped, and anything that can be a plugin is a plugin. A PDF writer is larger than the entire grid; a formula engine is larger still. So rather than ship a mediocre built-in, the grid exposes the seam you can drive an external library from:
| Capability | Seam |
|---|---|
| PDF export | ExportPlugin.getResolvedColumns() / .export() |
| Computed & formula columns | column.valueAccessor |
| Charts and rich cell content | column.renderer |
| Masked, validated or exotic input | column.editor + the cell-commit event |