Josh Kelley 5eb3682b9f
Give elements their own interface definition (#8290)
From what I understand, if we want to allow registering additional element options (see [here][1] for an example), then the element options need to be a top-level interface so that they can be used with TypeScript's [declaration merging][2].

[1]: https://github.com/chartjs/chartjs-plugin-annotation/pull/275#issuecomment-742754562
[2]: https://www.typescriptlang.org/docs/handbook/declaration-merging.html
2021-01-30 14:48:18 -05:00
2020-12-19 12:52:18 -05:00
2020-09-28 09:11:55 -04:00
2020-09-28 09:11:55 -04:00
2020-10-16 07:40:49 -04:00
2021-01-03 10:23:29 -05:00


Simple yet flexible JavaScript charting for designers & developers

Downloads GitHub Workflow Status Coverage Awesome Slack

Documentation

Currently, there are two versions of the library (2.9.4 and 3.x.x). Version 2 is the latest stable version while 3 is the next (currently beta) version. As such bear the following in mind:

  • Current docs points to version 2.9.4
  • Npm/CDN/etc point to version 2.9.4 (unless you explicitly set newer version, e.g. npm next)
  • Source currently points to 3.x.x version. 2.9.4 source is available here
  • Docs for version 3.x.x are available here

Contributing

Instructions on building and testing Chart.js can be found in the documentation. Before submitting an issue or a pull request, please take a moment to look over the contributing guidelines first. For support, please post questions on Stack Overflow with the chartjs tag.

License

Chart.js is available under the MIT license.

Description
Simple HTML5 Charts using the tag
Readme 67 MiB
Languages
JavaScript 89%
TypeScript 10.6%
Shell 0.2%
HTML 0.2%