Contributions to Chart.js are welcome and encouraged, but please have a look through the guidelines in this document before raising an issue, or writing code for the project.
The issue tracker is the preferred channel for reporting bugs, requesting new features and submitting pull requests.
If you're suggesting a new chart type, please take a look at writing new chart types in the documentation or consider creating a plugin.
To keep the library lightweight for everyone, it's unlikely we'll add many more chart types to the core of Chart.js, but issues are a good medium to design and spec out how new chart types could work and look.
Please do not use issues for support requests. For help using Chart.js, please take a look at the chartjs
tag on Stack Overflow.
Well structured, detailed bug reports are hugely valuable for the project.
Guidlines for reporting bugs:
Please provide any additional details associated with the bug, if it's browser or screen density specific, or only happens with a certain configuration or data.
Run npm install
to install all the libraries, then run gulp dev --test
to build and run tests as you make changes.
Clear, concise pull requests are excellent at continuing the project's community driven growth. But please review these guidelines and the guidelines below before starting work on the project.
Be advised that Chart.js 1.0.2 is in feature-complete status. Pull requests adding new features to the 1.x branch will be disregarded.
Guidelines:
/src
, not Chart.js
or Chart.min.js
in the repo root directory, this avoids merge conflicts.md
file in /docs
By contributing your code, you agree to license your contribution under the MIT license.