Reevaluate chart libraries #923
Labels
For: Frontend
This is something to do for the front end (client folder) of the website.
Priority: Low
Something not very essential to the release, can be done in free time and bumped back if needed.
Type: Dev/Internal
Something that is more internal to development than end user facing.
Whilst doing the map approval section of the map edit page, I used Chart.JS as I wanted something quite and easy, and PrimeNG comes with a wrapper component for it.
However Chart.JS is canvas-based, looks crappy by default, and can't be configured much. I probably should've stuck with echarts, but to be totally honest, I completely forgot it existed and picked between chart.js and D3/D3 derivatives.
We intend to do a lot more graphing in the future, just because I picked Chart.JS for this simple thing shouldn't mean we get stucked with Chart.JS in the future. My hunch is we'll go with ECharts.
The text was updated successfully, but these errors were encountered: