XLSX export: optional native Excel PivotTable
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 20/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 活跃
- 技术栈
- javascript, openapi, react
调研方向
Read the XLSX writer and the export paths for the UI, CLI, REST, and MCP render_view mentioned in the issue, then inspect how exportData and the REST/MCP exposure policies are enforced. The issue leaves the design, size limits, and OOXML implementation open; first define those decisions and test how generated files open in Excel, LibreOffice, and Numbers without repair prompts. Done means an optional PivotTable export respects exposure controls and faithfully represents unsupported view features.
由索引模型根据 Issue 内容生成。
描述
Today the XLSX export writes the pivot result as a plain table. Some people want to keep working in Excel: open the file and change rows, columns and filters there. For that the workbook needs a real Excel PivotTable.
Idea: an optional export "Workbook with Excel PivotTable" (UI, CLI --format xlsx --pivot-table, REST/MCP render_view):
- a data sheet with the rows the view needs, a pivot cache over it (
pivotCacheDefinition,pivotCacheRecords) and a pivot table (pivotTable) laid out like the view: rows, columns, values with their aggregation, filters as page fields or item selections; - what has no Excel equivalent (derived fields such as "Date by month", show-as, value filters on totals, relative dates) is either written as a helper column or listed in a note sheet, never silently dropped;
- the chart (#360) could become a PivotChart on the same cache.
Open points:
- The file then contains the source rows, not only the result. That must follow
exportDatain the UI and the exposure policy (summary/hide,results) in REST and MCP, and is off by default. - The XLSX writer is hand-written (no SheetJS, no ExcelJS); the pivot parts are a larger piece of OOXML to write and test, including Excel, LibreOffice and Numbers opening it without a repair prompt.
- Size limits for the data sheet.
Related: #360, #364.
- 主要语言
- JavaScript
- 星标
- 1
- 派生
- 1
- 平均合并
- 3 小时 34 分钟
- 30 天内合并 PR
- 213
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
eizedev/pivotkit 的其他 Issue
-
area:server enhancement
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复
-
area:server bug
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
area:server enhancement
难度 2/5 1-3 小时 新手友好度 66/100
维护者通常 1 天内回复
-
documentation idea
难度 2/5 1-3 小时 新手友好度 84/100
维护者通常 1 天内回复
-
area:tests idea
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
相似的 Issue
-
入群码过期未关闭
难度 1/5 1 小时以内 新手友好度 84/100
aliyun/ai-agent-handbook#29 · 1 条评论 ·
-
docs documentation need-triage SaaS
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 76/100
apache/cloudstack#14719 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 3 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复