This project will be lightly maintained by the original author. Contributions are welcome.
This is not an official Google product.
- Add missing constructors of
Regenerated API for Chart.js 2.6.0
Support Dart 2.
- Allow the latest release of
Fixed strong-mode issues.
- Regenerated API from an updated
- Updated to Chart.js 2.4.0
- Updated to Chart.js 2.3.0
- Generated using dart_js_facade_gen.
Fixes for Dart 1.16 JS interop requirements.
Experimented with adding
BREAKING Includes complete
- Updated for Dart 1.13 release.
- Initial release
An example of using Chart.js.
This example is ported from this sample in the
To view the example, run
pub serve example from the root directory of this project – the directory containing
> pub serve example Loading source assets... Serving js example on http://localhost:8080 Build completed successfully
You can view it with Dartium or any other browser.
Use this package as a library
1. Depend on it
Add this to your package's pubspec.yaml file:
dependencies: chartjs: ^0.5.1
2. Install it
You can install packages from the command line:
$ pub get
Alternatively, your editor might support
Check the docs for your editor to learn more.
3. Import it
Now in your Dart code, you can use:
Describes how popular the package is relative to other packages. [more]
Code health derived from static analysis. [more]
Reflects how tidy and up-to-date the package is. [more]
Weighted score of the above. [more]
We analyzed this package on Nov 15, 2019, and provided a score, details, and suggestions below. Analysis was completed with status completed using:
- Dart: 2.6.0
- pana: 0.12.21
Detected platforms: web
Health issues and suggestions
Document public APIs. (-0.76 points)
739 out of 745 API elements have no dartdoc comment.Providing good documentation for libraries, classes, functions, and other API elements improves code readability and helps developers find and use your API.
dartfmt to format
The package description is too short. (-20 points)
Add more detail to the
description field of
pubspec.yaml. Use 60 to 180 characters to describe the package, what it does, and its target use case.