Use when developing or modifying the @handsontable/angular-wrapper package - Angular components with decorators, NgZone performance optimization, and ng-packagr build system
日本語の概要は準備中です。原文の説明を表示しています。
Use when creating or modifying a Handsontable cell renderer function that controls how cell content is displayed in the DOM - pure functions that take cell data and modify TD element
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Renderers are pure functions, no class or state:
function myRenderer(hotInstance, TD, row, col, prop, value, cellProperties) {
baseRenderer.apply(this, arguments);
// Modify TD element here
}
Call baseRenderer first: it applies the readonly and invalid CSS classes, ARIA attributes, and other standard cell setup.
fastInnerText(TD, value) from src/helpers/dom/element.ts (XSS-safe).innerHTML.getCellContentRoot(TD) when managing the cell's children (empty(...), appendChild(...), insertBefore(x, root.firstChild)). A row at an exact height keeps content in a div.htCellClip wrapper; the helper returns it when present and the cell otherwise. Writing straight into TD rebuilds the wrapper every draw, and a node left outside it grows the row back. fastInnerText/fastInnerHTML do this on their own. Models: checkboxRenderer, autocompleteRenderer, multiSelectRenderer.null and undefined values.src/renderers/{rendererName}/
{rendererName}.ts # Renderer function
index.ts # Re-exports
Registry: src/renderers/registry.ts.
import { registerRenderer } from '../../renderers/registry';
registerRenderer('myRenderer', myRenderer);
src/renderers/baseRenderer/baseRenderer.tssrc/renderers/textRenderer/textRenderer.ts - simplest, good template.src/renderers/htmlRenderer/htmlRenderer.ts - raw HTML.src/renderers/numericRenderer/numericRenderer.ts - numeral.js formatting.Renderers run for every viewport cell on every render cycle (fast and slow).
getBoundingClientRect, offsetWidth) outside the renderer to avoid layout thrashing.TD elements and rewrites them on scroll, so a TD-keyed cache (WeakMap or a property on it) misses almost every call (issue #13446). Two traps: getSourceDataAtRow() returns a copy on every call, so it cannot be a WeakMap key; read the record from your own data array by toPhysicalRow(row) (the cell value IS passed by reference). afterRender does not fire for scroll draws; count or refresh per-draw state in afterViewRender. Worked example: docs/content/recipes/performance/expensive-cell-renderer/.まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Use when developing or modifying the @handsontable/angular-wrapper package - Angular components with decorators, NgZone performance optimization, and ng-packagr build system
日本語の概要は準備中です。原文の説明を表示しています。
Use when testing a local or public URL on a real device via BrowserStack, opening a live browser session on Android, iOS, or desktop browsers, or when the user mentions BrowserStack, real device testing, mobile testing, cross-browser testing, touch testing, or wants to verify behavior on a specific phone, tablet, or browser version. Also trigger when the user says "test this on Android/iPhone/Safari/Chrome mobile", asks to open a live session, or mentions demo-mobile.html, even if they don't mention BrowserStack by name.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a source code change needs a changelog entry, or before committing and pushing any bug fix, feature, or behavior change to source code - detecting when entries are required, categorizing changes correctly (added/changed/fixed/deprecated/removed/security), writing user-facing titles, and creating the JSON entry in .changelogs/
日本語の概要は準備中です。原文の説明を表示しています。
Query the pre-built code-review-graph knowledge graph (Tree-sitter, whole monorepo) instead of walking call chains with Grep+Read – 2-6x cheaper, and it catches dynamic dispatch that grep misses. Use for ANY task that spans multiple files, even when the user never mentions a graph or asks for it - fixing or tracing a bug ("fix this bug", "why does X happen", "trace this"), exploring unfamiliar code ("how does X work", "who calls X", "what imports Y", "where is X used or handled"), planning or doing a refactor ("rename X", "is it safe to change or remove X", "what would break", "blast radius", "find dead code"), or reviewing changes ("review this PR", "review this branch or diff"). When you are about to Grep for a symbol's callers, callees, or importers, use this skill.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with row or column indexes in Handsontable - translating between physical, visual, and renderable coordinates, using IndexMapper, or debugging index-related bugs where rows or columns appear in wrong positions
日本語の概要は準備中です。原文の説明を表示しています。
Use when creating code examples for documentation pages - JavaScript, TypeScript, React, Angular, and Vue variants with proper imports, registration, and license key
日本語の概要は準備中です。原文の説明を表示しています。