gionkunz/chartist-js Chartist js

Simple responsive charts

#63 (all)
JavaScript (change)
14 seconds
about 2 years ago

This page shows an evaluation of the project's documentation.

Each class, module, method, etc. is given a grade based on how complete the docs are.

The bar above shows the distribution of these grades.

JavaScript support is still young. Please report any mistakes Inch makes!
Seems really good
Chartist.Svg.Path.curve in /src/scripts/svg-path.js N
Chartist.Svg.Path.arc in /src/scripts/svg-path.js N
Chartist.Svg.Path.translate in /src/scripts/svg-path.js Ne
Chartist.Svg.Path.scale in /src/scripts/svg-path.js Ne
Chartist.Svg.Path.line in /src/scripts/svg-path.js Ne
Show 55 more ...
Proper documentation present
Chartist.Core.Chartist.serialMap in /src/scripts/core.js E
Chartist.Core.Chartist.splitIntoSegments in /src/scripts/core.js E
Chartist.Core.Chartist.isFalseyButZero in /src/scripts/core.js E
Chartist.Core.Chartist.isNum in /src/scripts/core.js E
Chartist.Svg.foreignObject in /src/scripts/svg.js E
Show 20 more ...
Please take a look
projectValue in /src/scripts/axes/axis.js E

Let's raise the visibility of documentation in Open Source!

This page is for gionkunz/chartist-js and is part of a project called "Inch CI", showing documentation measurements provided by Inch. Inch CI also provides a badge: (not counting low priority objects)

Can I have my own badges?

Sure! To get the badge for the project you are looking at, just click the badge next to the project name.

To register another project with Inch CI, just enter your username/repo on the homepage or sign in with GitHub!

Can I tell Inch which files to evaluate?

No problemo! Learn how ...

Can I configure a webhook for continuous integration?

Of course! Learn how ...

What is the goal of this?

I really think that posting badges for documentation in READMEs will benefit you (because people can see that your project is well documented) and our community in general by improving the visibility of documentation.

Let's start a discussion, let's raise the visibility of documentation, let's talk.

Suggestions, feedback, critique: Hit me up on Twitter or via issue.