XLSX export: optional native Excel PivotTable

Aberta
#372 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
20/100
Tipo de issue
Funcionalidade
Clareza
Precisa de esclarecimento
Status de atividade
Ativa
Stack de tecnologia
javascript, openapi, react

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

area:core area:report enhancement idea

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 exportData in 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.

Linguagem predominante
JavaScript
Estrelas
1
Forks
1
Merge médio
3h 21min
PRs com merge (30d)
250

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de eizedev/pivotkit

Todas as issues de eizedev/pivotkit

Issues semelhantes

Mais issues de JavaScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.