What problem does this feature solve?
After automatically generating a chart configuration with vmind.generateChart, users want to:
- Dynamically re-fetch or transform data on the frontend using libraries like alasql , based on the original field semantics.
- Decouple chart configuration from static data, allowing charts to adapt when data sources evolve.
This is especially useful in low-code platforms, dashboards, or BI tools where chart templates should remain reusable across changing datasets.
What does the proposed API look like?
Support Returning SQL Field Information in vmind.generateChart
What problem does this feature solve?
After automatically generating a chart configuration with vmind.generateChart, users want to:
This is especially useful in low-code platforms, dashboards, or BI tools where chart templates should remain reusable across changing datasets.
What does the proposed API look like?
Support Returning SQL Field Information in vmind.generateChart