Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reevaluate chart libraries #923

Open
tsa96 opened this issue Mar 17, 2024 · 0 comments
Open

Reevaluate chart libraries #923

tsa96 opened this issue Mar 17, 2024 · 0 comments
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.

Comments

@tsa96
Copy link
Member

tsa96 commented Mar 17, 2024

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.

@tsa96 tsa96 added 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. For: Frontend This is something to do for the front end (client folder) of the website. labels Mar 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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.
Projects
None yet
Development

No branches or pull requests

1 participant