[Feature] Support for LLM-optimized Declarative Protocol (ECharts-Lite) in Markdown/JSON
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 25/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Necesita aclaración
- Estado de actividad
- Tranquilo
- Stack tecnológico
- json, markdown, typescript
- Área
- data-visualization
Línea de trabajo
Start with the proposed echarts.renderLite(dom, liteOption, theme) entry point and the echarts-lite/v1 schema described in the issue. Define the Markdown/JSON input and strict validation boundaries, then trace how chart types and dataset dimensions should expand into an ECharts option. Done means a consistent protocol with smart defaults and clear validation errors.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
What problem does this feature solve?
[Context & Rationale]
With the rapid integration of Large Language Models (LLMs) into data analysis and BI tools, ECharts has become a primary target for AI-generated visualizations. However, there is a significant "impedance mismatch" between LLM outputs and the current ECharts option structure. The existing API, while powerful and comprehensive, is highly verbose for LLMs, leading to frequent "hallucinations" in nested JSON structures, high token consumption, and instability in rendering styling details.
[End User Experience]
The goal is to enable a "Zero-Config" experience for AI-native applications. Developers should be able to pass a simplified, intent-based Markdown or JSON structure directly from the LLM to ECharts. The renderer should intelligently handle the "boilerplate" (like tooltips, basic axis styling, and grid layouts) based on the chart type and data, allowing the LLM to focus solely on the data and the high-level visual intent.
[Why it cannot be easily dealt with existing APIs]
While users can write custom "translation" layers, every developer is currently reinventing the wheel. A fragmented ecosystem of "ECharts-Lite" parsers leads to inconsistent user experiences across different AI platforms. By introducing a standardized, declarative "Lite" protocol within the ECharts ecosystem, we can:
Lower the barrier for AI agents to interact with ECharts.
Optimize performance by reducing the payload size in LLM streaming.
Ensure visual consistency by separating data (from LLM) and theme/style (from the developer/ECharts defaults).
What does the proposed API look like?
We propose a Simplified Declarative Schema (e.g., echarts-lite) that can be used either as a standalone JSON or within a Markdown code block. This schema prioritizes a flat structure and the dataset component.
Proposed Schema Example:
JSON
{
"protocol": "echarts-lite/v1",
"type": "line",
"title": "User Growth Trend",
"data": [
["Month", "Users", "Retention"],
["2025-01", 150, 0.85],
["2025-02", 230, 0.82],
["2025-03", 224, 0.88]
],
"options": {
"smooth": true,
"stack": false,
"showSymbol": "auto"
},
"enhance": ["tooltip", "legend", "toolbox"]
}
Implementation Suggestion:
A new static method or a lightweight plugin, e.g., echarts.renderLite(dom, liteOption, theme), which:
Expands the lite protocol into a full echarts.option object internally.
Injects smart defaults for missing UI configurations (e.g., automatically generating series based on the data dimensions).
Validates the input using a strict JSON Schema to provide clear error messages for LLM debugging.
- Lenguaje dominante
- TypeScript
- Estrellas
- 67.7k
- Forks
- 19.9k
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de apache/echarts
-
[Bug] String formatter templates only replace the first occurrence of `{a}`/`{b}`/`{c}`Posiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abiertoen pending
Dificultad 2/5 1-3 horas Aptitud para principiantes 80/100
-
[Bug] Inverse axis collapses the grid with outerBoundsContain when a tick is near the axis edgePosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abiertoen pending
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
-
en pending
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
-
en pending
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
-
[Bug] The zoom cursor in the toolbox area is incorrectPosiblemente ocupada @waterWang la tomó hace 98 días. Abiertobug en pending
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
Todos los issues de apache/echarts
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 83/100
pollen-robotics/reachy-mini-desktop-app#341 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 2 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
mike-north/AgentMonitors#648 ·
Los mantenedores suelen responder en 1 día
-
Position: a popup placed again from between two layout steps lands a fraction of a pixel offAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
vercel-labs/ui#700 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Los mantenedores suelen responder en 2 días