Syncfusion Angular Spreadsheet Editor

Syncfusion Angular Spreadsheet Editor

Overview

This skill helps developers generate Angular code for integrating the Syncfusion Spreadsheet Editor into their applications. It provides ready-to-use code snippets, API guidance, and best practices for building Excel-like functionality in Angular projects.

Key Capabilities

• File Operations: Import/export Excel files (xlsx, xls, xlsb), CSV files, and PDF export
• Data Management: Data binding, editing, sorting, filtering, and validation
• Cell Operations: Formatting (fonts, colors, borders, alignment), merge cells, wrap text
• Formulas & Calculations: Built-in Excel formulas, custom functions, named ranges
• Collaboration: Notes, comments, and threaded discussions
• Advanced Features: Charts, images, hyperlinks, conditional formatting, freeze panes, sheet protection, virtualization for large datasets

Quick Start Examples

Example 1: Generate Spreadsheet with Formatting

User: "Create a Spreadsheet with data and apply cell styles"

Result: An Angular component code snippet is generated that loads provided data into the Spreadsheet and applies basic cell formatting.

Example 2: Generate Code for Loading a File

User: "Create a Spreadsheet and load an Excel file initially"

Result: An Angular component code snippet is generated that initializes the Spreadsheet and programmatically opens an Excel file on startup.

Getting Started — Minimal Angular Code

Minimal Angular setup using Standalone Component (Angular 14+):

app.ts

import { Component, ViewChild } from '@angular/core';
import { SpreadsheetAllModule, SpreadsheetComponent } from '@syncfusion/ej2-angular-spreadsheet';

@Component({
  selector: 'app-root',
  standalone: true,
  imports: [SpreadsheetAllModule],
  template: `
    <ejs-spreadsheet #spreadsheet (created)="created()">
      <e-sheets>
        <e-sheet>
          <e-rows>
            <e-row>
              <e-cells>
                <e-cell value="Hello, Spreadsheet!"></e-cell>
              </e-cells>
            </e-row>
          </e-rows>
        </e-sheet>
      </e-sheets>
    </ejs-spreadsheet>
  `
})
export class AppComponent {
  @ViewChild('spreadsheet') spreadsheet!: SpreadsheetComponent;

  created(): void {
    // All post-initialization code goes here
  }
}

Placeholders:

• #spreadsheet — Angular template reference variable for the component
• <e-sheets> — declarative sheet definitions with rows and cells
• created() — event handler called after the Spreadsheet is fully initialized

Note: Always import SpreadsheetAllModule in the imports array of the standalone component for all features to work correctly.

Generate Angular Code for the User's Project

Trigger keywords: "angular spreadsheet", "spreadsheet editor", "syncfusion spreadsheet", "excel component", "load excel file", "open excel file", "import excel", "export excel file", "save excel", "export to pdf", "export to csv", "view excel", "configure spreadsheet", "create spreadsheet", "add spreadsheet", "spreadsheet data", "cell formatting", "apply formulas", "insert chart", "data binding", "spreadsheet validation", "freeze panes", "protect sheet"

Workflow:

1. Identify the requested Spreadsheet feature (data binding, formulas, charts, export, etc.).

2. Read the relevant references/*.md file(s) to understand the APIs and code patterns for the requested feature.

   • For create, initialize, render, package setup, CSS setup, or basic Spreadsheet requests, read references/getting-started.md first.

3. STOP before generating code, installing packages, creating files, or modifying project files. Check if the user has already chosen a delivery mode.

4. If no delivery mode is chosen yet, you MUST ask the user first using this concise multiple-choice question:

   "How would you like to receive the generated Spreadsheet code?"

   • Option 1: Replace the code in a specific project file (you'll need to provide the file path and confirm)
   • Option 2: Save the code in this skill's output folder at {skill-root}/syncfusion-angular-spreadsheet-editor/output/app.ts (and related files)
   • Option 3: Share the code directly in the chat window

5. If the user selects Option 1, validate the provided project file/folder path before generating or replacing code.

   • If the provided path is an existing Angular project and contains package.json, continue with the previous behavior.
   • If the provided path is an empty folder or does not contain an Angular project, do not edit files and do not end the chat.
   • Explain that an Angular project is required before replacing project files.
   • Ask whether the user wants to set up/install Angular first using references/getting-started.md.
   • Do not create project files, install packages, or run setup commands automatically unless the user explicitly confirms.

6. Only after the user selects a delivery mode and Option 1 path validation is complete, proceed to generate Angular code using the APIs and snippets from references/*.md, substituting concrete placeholders from the user's project.

7. Scope implementations within the created event handler — All code implementations should be placed within the Spreadsheet's created event unless the user explicitly requests a different event handler (e.g., beforeSave, cellSave, etc.).

8. Do NOT make changes to workspace project files unless the user explicitly chose Option 1, provided a valid Angular project file/folder path, and gave permission.

9. If no Angular project or package.json is detected, explain that an Angular project is required first and provide setup guidance from references/getting-started.md. Do not create project files, install packages, or run setup commands automatically unless the user explicitly requested Angular app creation and provided permission.

10. Create a new Angular application/project only when the user explicitly asks for it, such as:

• "create an Angular application and render Spreadsheet"
• "create a new Angular app with Spreadsheet"
• "create Angular app and add Spreadsheet"
• "set up a Spreadsheet app from scratch"

If the user only asks to create, add, render, or configure the Spreadsheet component, do not scaffold a new Angular application. Treat it as Spreadsheet component/code generation for an existing Angular project. 11. When generating code for an existing Angular project, include required package and CSS setup guidance from references/getting-started.md. 12. Provide complete Angular snippets and concise integration steps after delivering the code.

Refer to ## Rules section for operational constraints (output directory, temporary files, allowed libraries, etc.)

Code References

All code snippets and examples are in the references/ folder. Each file contains:

• Minimal Angular Code — a working, ready-to-use snippet
• Placeholders — values the user must customize
• Notes — Angular best practices and constraints

Key Rules for Code Generation (Angular-first)

1. Angular-first snippets — All examples and snippets must be written in Angular (TypeScript with inline template) and compile with the current @syncfusion/ej2-angular-spreadsheet npm package.

2. No inline code in this manifest — Refer to references/*.md for runnable snippets; keep this file as the concise policy and index.

3. Default event scoping — All implementations must be placed within the Spreadsheet's created event handler unless the user explicitly requests implementation in another event (e.g., beforeSave, cellSave, etc.). This ensures all operations occur after the Spreadsheet component is fully initialized.

4. Standalone component — Always use standalone: true with imports array inside the component. Never generate NgModule or app.module.ts or app.component.css based code.

5. Reference file requirements — Each reference must include:

   • Minimal Angular Code (complete, runnable — standalone component with inline template)
   • Placeholders (clearly marked values to replace)
   • Notes (Angular integration steps and best practices)

6. License handling — Do not hardcode license keys; refer users to env variables or project config.

7. Preserve data integrity — Preserve existing formulas, references, and formatting when generating or editing sheets.

8. No hallucinated APIs — Use verified Syncfusion Spreadsheet Editor method names only.

9. Read references first — For any requested feature, always read the relevant references/*.md file(s) first before generating code.

10. Build strictly from references — Build Angular code strictly from the APIs, methods, properties, events, and snippets found in the reference files. Do NOT invent, guess, or suggest any API, method, property, or event not explicitly present in the reference files.

Rules

• Output files must go in {skill-root}/syncfusion-angular-spreadsheet-editor/output/ directory when user selects Option 2
• Only use Syncfusion Spreadsheet APIs — never recommend or use alternative spreadsheet libraries (e.g., handsontable, ag-grid, luckysheet)
• No temporary files — never create temporary scripts, intermediate files, or scaffolding outside the output directory
• Angular-only code — all generated code must be valid Angular TypeScript with Angular template syntax, never generate vanilla JavaScript, jQuery, or non-Angular patterns
• Option 1 path validation: When the user selects Option 1, always validate the provided project file/folder path before editing or replacing files.
  • If the path contains an existing Angular project with package.json, continue with the normal code replacement flow.
  • If the path is empty or does not contain an Angular project, do not edit files and do not end the chat.
  • You MUST respond with a follow-up question instead of stopping.
  • Explain that an Angular project is required before replacing project files.
  • Ask whether the user wants setup guidance or wants to set up/install Angular first using references/getting-started.md.
  • Do not create project files, install packages, or run setup commands automatically unless the user explicitly confirms.
• Angular app creation constraint: Create or scaffold a new Angular application only when the user explicitly asks for Angular app/project creation, such as “create an Angular application and render Spreadsheet” or “create Angular app and add Spreadsheet”. For normal prompts like “create a spreadsheet with data” or “add Spreadsheet”, treat the request as component code generation for an existing Angular project.