Use when developing or modifying the @handsontable/angular-wrapper package - Angular components with decorators, NgZone performance optimization, and ng-packagr build system
日本語の概要は準備中です。原文の説明を表示しています。
Use when modifying the Walkontable rendering engine in src/3rdparty/walkontable/ - overlay system, viewport calculations, scroll handling, DOM management, or the TableView bridge between core Handsontable and Walkontable
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Walkontable is the rendering engine (viewport calculation, DOM rendering, scroll sync, overlays). Rules and traps live in handsontable/src/3rdparty/walkontable/AGENTS.md; architecture in handsontable/src/3rdparty/walkontable/.ai/ARCHITECTURE.md and .ai/CONCERNS.md.
Source is TypeScript in src/3rdparty/walkontable/src/, excluded from the main tsconfig.json, with its own build/test pipeline. The bridge to core is TableView in src/tableView.ts. Plugins and core reach Walkontable only through TableView or the public Core API. Inside Walkontable, wrap DOM logic in abstraction modules.
wire.ts is the single composition root: buildContext(wot) returns an EngineContext. Each module has a co-located factory create<Module>Deps(ctx); its type is inferred.
// scroll/scroll.ts: the only place Scroll's deps are declared
export function createScrollDeps(ctx: EngineContext) {
return { wtSettings: ctx.wtSettings, geometryReader: ctx.geometryReader, getWtTable: ctx.getWtTable /* … */ };
}
export type ScrollDeps = ReturnType<typeof createScrollDeps>;
class Scroll {
#deps: ScrollDeps;
constructor(deps: ScrollDeps) { this.#deps = deps; }
}
#deps; take a single deps constructor argument (plus at most one per-instance identity arg: table name, overlay type, event parent, corner-overlay sibling refs).*Deps type with ReturnType<typeof createXDeps>.get deps() over #deps only where JS forces external reach: a base class whose subclasses need it (Overlay), runtime mixins (Table), or a helper read by a collaborator (RowUtils, ColumnUtils).getWtViewport()). Volatile per-draw objects (calculator, filter) go stale; read volatile ranges fresh off the owner (see the rowRangeQuery/columnRangeQuery mixins in table/rangeQuery/virtualRange.ts).scroll/scroll.ts is the simplest template.GeometryReader proxyLayout-forcing reads go through the injected reader: getBoundingClientRect, getClientRects, getComputedStyle, offsetWidth/offsetHeight/offsetTop/offsetLeft/offsetParent, clientWidth/clientHeight, scrollWidth/scrollHeight, and the helpers/dom/element measurement helpers (offset, outerWidth/outerHeight, element innerWidth/innerHeight, getMaximumScrollTop/getMaximumScrollLeft, getScrollbarWidth, getStyle). The reader is the seam a future per-draw CachingGeometryReader replaces.
Scroll-position and window-viewport reads are read directly: scrollX/scrollY/pageXOffset/pageYOffset, element scrollTop/scrollLeft, window innerWidth/innerHeight. For a polymorphic element-or-window scroll position use the raw getScrollLeft/getScrollTop helper (it also survives an iframe realm boundary, where the instanceof Window-gated helper returns undefined).
const rect = this.#deps.geometryReader.getBoundingClientRect(el);
const w = this.#deps.geometryReader.offsetWidth(el);
const top = rootWindow.scrollY; // direct
Reader handles: this.#deps.geometryReader (most modules), this.deps.geometryReader (overlays/table), wotInstance.domBindings.geometryReader when only the instance is in hand (utils/pointerToCoords.ts, selection/border/border.ts).
Writes (el.scrollTop = n, el.style.x = …) and this.<field> (stored state, even when named clientHeight/scrollTop) are direct.
When the proxy lacks a method for a layout-forcing read, add it to both domMeasure/geometryReader.ts (interface) and domMeasure/liveGeometryReader.ts (live adapter), then use it.
ESLint rule handsontable/no-direct-dom-geometry-read (error) covers all of src/3rdparty/walkontable/src except domMeasure/**. The rule lives in handsontable/.config/plugin/eslint/rules/ and is a pnpm file: dependency that is copied, not symlinked: after editing the rule (or on a checkout that predates it) run pnpm install, or eslint fails with "definition not found".
.ai/CONCERNS.md before touching overlay positioning or synchronization.requestAnimationFrame batching).The engine predicts scrollbars from numbers instead of render, measure, re-render:
viewport/boxLayout/: resolveLayout() is a pure function solving the workspace / inner / viewport / hider box decomposition and the two-variable scrollbar fix-point into an immutable LayoutSnapshot. gatherLayoutInput.ts is the one impure adapter. Viewport.beginDrawLayout() resolves the snapshot once per master draw, after the size caches are built and before the calculators run.axisSizing/: intended size of one row/column: AxisSizeSource port (axisSizeSource.ts, defaultSizeSource.ts), prefix-sum caches (positionCache.ts), border-box conversion (boxModel.ts), size getters and oversized-content measurement (sizeGetters.ts, oversizedRows.ts).singlePassLayout escape hatch. The prediction is used only in element mode with uniform sizes and the singlePassLayout setting on. TableView sets it to false whenever mergeCells is enabled (a virtualized merged cell's height depends on the viewport being computed); window-scrolled tables fall back to measurement too. Any new method that reads getLayout() must branch on singlePassLayout and window mode and fall back to a direct DOM measure otherwise; without that branch, merged-cell and window-scrolled tables break. Viewport.usesLayoutSnapshotForCalculators() is the gate predicate.
Draw orchestration: table/drawCycle.ts; Table.draw() delegates to the class-free runDrawCycle(table, fastDraw).
.ai/CONCERNS.md)wire.ts. Pass narrow deps objects, never the whole wot god-object.wot decoupling is deferred: overlays still reach the master via this.wot.wtTable/.wtViewport/.wtOverlays. The Clone is a second Walkontable instance holding a handle to the master. Leave both until the planned stage.requestAnimationFrame.forEach loop instead of arr.push(...largeArray) at 10k+ elements.Walkontable has its own runner, separate from the main E2E pipeline.
npm run test:walkontable --prefix handsontablesrc/3rdparty/walkontable/test/src/3rdparty/walkontable/test/ may be edited; new coverage goes to tests/e2e/walkontable/*.spec.ts with a page object in tests/fixtures/pages/walkontable/ (tier reference: frozen-column-row-heights.spec.ts + FrozenTallCellPage.ts). A page-object method that scrolls ends on a render-state probe (first rendered row, a draw counter) instead of scrollTop, because the redraw is rAF-batched and lands after the scroll position settles. Copy OverlaysPage.scrollToEnd() (ends on the last cell being rendered); FrozenTallCellPage.scrollVerticallyTo() ends on scrollTop, so its spec polls masterFirstRenderedRow() itself after every scroll. Rules: handsontable-playwright-e2e, references/determinism.md.| Path | Purpose |
|---|---|
src/3rdparty/walkontable/src/ | All Walkontable source |
src/tableView.ts | Bridge to core (the boundary for plugins) |
src/3rdparty/walkontable/src/overlay/ | Overlay system |
src/3rdparty/walkontable/src/render/ | DOM rendering |
src/3rdparty/walkontable/src/viewport/boxLayout/ | Layout snapshot + scrollbar fix-point solver |
src/3rdparty/walkontable/src/axisSizing/ | Size sources, prefix-sum caches, box model |
src/3rdparty/walkontable/src/domMeasure/ | GeometryReader proxy + live adapter |
src/3rdparty/walkontable/src/table/drawCycle.ts | runDrawCycle |
src/3rdparty/walkontable/src/wire.ts | Composition root (buildContext → EngineContext) |
GeometryReader proxy.*Deps interface, or passing the whole wot into a module.#method of MasterTable from a path the base Table constructor reaches. Table's constructor calls alignOverlaysWithTrimmingContainer() before MasterTable's own fields exist, so a #method call there throws Receiver must be an instance of class MasterTable (the brand check fails like a #field read). Guard field reads with the existing fieldsInitialized check (#trimmingCache in this), and put logic that must run on that path in a module-level function that takes the table (alignHolderWithSplitOwners(table, …) in table/regions/masterTable.ts is the pattern).this.trimmingContainer on an overlay to decide something about the other axis. Each region overlay holds the owner of its own axis only (top/bottom → vertical, inline-start → horizontal), and the two can differ; ask wtViewport.isVerticallyScrollableByWindow() / isHorizontallyScrollableByWindow(). Rules and split mode: "Per-axis trimming containers" in handsontable/src/3rdparty/walkontable/AGENTS.md.When a function receives a value whose shape varies, make the signature generic instead of casting with as SomeType (or <SomeType>value). For any, take a type parameter; use unknown at boundaries and narrow with a type guard.
function getFirst<T>(items: T[]): T { return items[0]; }
const row = getFirst(rows); // typed as UserRow
Narrow a Node | Element | null with isHTMLElement from src/helpers/dom/element.ts wherever you would write x as HTMLElement, x instanceof HTMLElement, or a nodeType === Node.ELEMENT_NODE guard. From Walkontable source the import is ../../../../helpers/dom/element (adjust ../ count to file depth).
if (isHTMLElement(node.nextSibling)) { /* HTMLElement here */ }
Fix the JSDoc/export in the .ts source and rerun npm run build:types; handsontable/tmp/ stays generated.
import type for typesimport type { ViewportColumnsCalculator } from './calculator/viewportColumns';
core/| Type | Location |
|---|---|
GridSettings, Events, HookKey | src/core/settings.ts |
HotInstance | src/core/types.ts |
Import them with import type; never paste a partial copy of GridSettings/HotInstance into the file you are editing (a local copy drifts from the real signature).
#; callbacks are arrow-function class fieldsclass Overlay {
#cachedWidth: number | null = null;
#onScroll = (): void => { /* `this` is bound */ };
}
@private JSDoc tags and .bind(this) are forbidden.
ESLint fails the build above it; extract a helper.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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
日本語の概要は準備中です。原文の説明を表示しています。