From 0f04ff60525a2b807adf71cf71afc7a6b6a40cf5 Mon Sep 17 00:00:00 2001 From: Claude Date: Mon, 24 Aug 2026 23:41:15 +0000 Subject: [PATCH] docs(core): name report-schema.mdx's subject ReportComponentSchema MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The page called its subject `ReportSchema` in four prose/frontmatter sites while its own example fence, its property tables (PR #6168) and the actual declaration all say `ReportComponentSchema` (packages/types/src/reports.ts:359). `ReportSchema` is not a dead name: `@objectstack/spec` exports it for the dataset-bound report shape (json-schema/ui/Report.json — name / label / dataset / rows / columns / values), which is what content/docs/plugins/plugin-report.mdx documents. A reader following the old name landed on a real but wrong declaration. `@object-ui/types` already re-exports that spec symbol under the prefixed name `SpecReportSchema` "to avoid collision", so the prose was the last place using the bare name for the component shape. Prose and frontmatter only. No source change, no fence touched. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_019b5UBNMtTzKbVtZZGvFuxe --- content/docs/core/report-schema.mdx | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/content/docs/core/report-schema.mdx b/content/docs/core/report-schema.mdx index 9c6f53173f..e9bebdc6f4 100644 --- a/content/docs/core/report-schema.mdx +++ b/content/docs/core/report-schema.mdx @@ -1,5 +1,5 @@ --- -title: "Report Schema (ReportSchema)" +title: "Report Schema (ReportComponentSchema)" description: "Enterprise reports with aggregation, export, and scheduling" --- @@ -7,11 +7,11 @@ import { SchemaExample } from '@/app/components/ComponentDemo'; # Report Schema -The `ReportSchema` enables creating comprehensive data reports with field aggregation, multiple export formats, and automated scheduling. +The `ReportComponentSchema` enables creating comprehensive data reports with field aggregation, multiple export formats, and automated scheduling. ## Overview -ReportSchema provides: +ReportComponentSchema provides: - **Field aggregation** - Sum, average, count, min, max, distinct - **Export formats** - PDF, Excel, CSV, JSON, HTML - **Scheduled reports** - Daily, weekly, monthly, quarterly, yearly @@ -455,7 +455,7 @@ if (result.success) { ## Use Cases -ReportSchema is perfect for: +ReportComponentSchema is perfect for: - **Analytics dashboards** - Display key business metrics and KPIs - **Business intelligence** - Generate insights from operational data