You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Brylie Christopher Oxley (JIRA)" <ji...@apache.org> on 2019/04/23 09:59:00 UTC

[jira] [Updated] (AIRFLOW-4392) Replace NVD3 with maintained library

     [ https://issues.apache.org/jira/browse/AIRFLOW-4392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brylie Christopher Oxley updated AIRFLOW-4392:
----------------------------------------------
    Description: 
The NVD3 charting library, while having a nice API and default charts, is no longer actively maintained. Also, the internal structure of the NVD3 library means that each chart type is treated as distinct, so the developer API may be inconsistent or lacking across different chart types.

It may prove beneficial to replace NVD3 with a charting library that:
 * is actively maintained
 * provides a unified (perhaps [data-centric|https://blog.taucharts.com/taucharts-data-focused-charting-library/]) API across chart types

  was:
The NVD3 charting library, while having a nice API and default charts, is no longer actively maintained. Also, the internal structure of the NVD3 library means that each chart type is treated as distinct, so the developer API may be inconsistent or lacking across different chart types.

It may prove beneficial to replace NVD3 with a charting library that:
 * is actively maintained
 * provides a unified (perhaps [data-centric|[http://example.com|https://blog.taucharts.com/taucharts-data-focused-charting-library/]]) API across chart types


> Replace NVD3 with maintained library
> ------------------------------------
>
>                 Key: AIRFLOW-4392
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-4392
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: webapp
>            Reporter: Brylie Christopher Oxley
>            Priority: Major
>
> The NVD3 charting library, while having a nice API and default charts, is no longer actively maintained. Also, the internal structure of the NVD3 library means that each chart type is treated as distinct, so the developer API may be inconsistent or lacking across different chart types.
> It may prove beneficial to replace NVD3 with a charting library that:
>  * is actively maintained
>  * provides a unified (perhaps [data-centric|https://blog.taucharts.com/taucharts-data-focused-charting-library/]) API across chart types



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)