Refactor Handsontable code by separating plugin responsibilities, reducing dependencies, batching rendering work, and updating coding patterns. It provides compatibility rules and testing guidance to preserve existing APIs, CSS classes, settings, and behavior.
Use when refactoring Handsontable code - applying SOLID principles, Law of Demeter, plugin extraction, performance optimization, code modernization, and API redesign with backward compatibility preservation
Review the instructions the agent will receive before you install.
Eliminate config that naming, location, or type conventions already express. Use auto-discovery or lifecycle hooks in place of new options or wiring.
isEnabled, enablePlugin, disablePlugin, updatePlugin, destroy, required static properties).hot.getPlugin('{Name}').hot.getPlugin('{Name}'), never by importing its class.this.hot.view.wt.wtTable.holder with a method on the intermediate layer.core.js or a large plugin outgrows one responsibility, move it to a dedicated plugin that communicates through new hooks.forEach loop in place of arr.push(...largeArray) (stack overflow at 10k+ elements).batch(), batchRender(), suspendRender()/resumeRender().requestAnimationFrame.#privateFields in place of @private JSDoc (exception: when # measurably hurts performance)..bind(this).?. only for values optional by design.| Rule | Detail |
|---|---|
| Default setting values stay unchanged | Defaults in metaSchema.ts. |
| Keep legacy CSS class names | Add new names alongside old ones; old names stay in the DOM. |
| Legacy API names keep working with no console warning | "Legacy", not "deprecated". |
| Deprecated APIs get a one-time warning | deprecatedWarn() from src/helpers/console.ts; works until the next major release. |
| Removed hooks go on the removed list | Users get a clear error instead of silent failure. |
src/helpers/ before writing new ones.*.unit.js): extracted helpers, strategies, pure logic.tests/e2e/*.spec.ts): feature still works in the browser. Edit an existing Jasmine *.spec.js only to keep it passing; never add a new one. A pure refactor with no behavior change can use a Refactor-only: <reason> commit trailer instead of a new test.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Develop and modify the Handsontable Angular wrapper with guidance on component lifecycle, settings updates, and NgZone, which controls change detection. It also covers standalone examples, global configuration, and the build and test workflow.
Open local or public web pages in BrowserStack Live for checks on real mobile devices or desktop browsers. The skill prepares temporary access to a local server, launches the requested session, and shares its dashboard link.
Prepare user-facing changelog entries for source code changes. The skill determines whether an entry is needed, classifies the change, writes a clear title, and uses the project CLI to create a JSON file tied to the pull request.
Explore relationships between functions and files using a prebuilt code graph, a map of code dependencies. Trace bugs, inspect callers and execution paths, and assess the impact of refactoring or proposed changes.
Work with Handsontable row and column positions by distinguishing source data, displayed order, and rendered cells. It guides index conversion and helps investigate misplaced data when sorting, filtering, hiding, or moving rows and columns.
Create Handsontable documentation examples for JavaScript, TypeScript, React, Angular, and Vue. The skill explains source files, generated JavaScript, required imports and license settings, embedding examples in guides, and checking that each framework version displays correctly.