#55 (all)
JavaScript (change)
8 seconds
4 months ago

Here are some suggestions where the project's documentation can be improved:

Proper documentation present
B
Promise#otherwise in /lib/decorators/flow.js E
B
Promise#progress in /lib/decorators/progress.js E
B
Promise#'yield' in /lib/decorators/flow.js E
B
Promise#orElse in /lib/decorators/flow.js E
B
Promise#done in /lib/decorators/flow.js E
B
Promise#tap in /lib/decorators/flow.js E
Undocumented
U
Promise#fold in /lib/decorators/fold.js Ne
U
Promise.onPotentiallyUnhandledRejectionHandled in /lib/decorators/unhandledRejection.js E
U
Promise.onPotentiallyUnhandledRejection in /lib/decorators/unhandledRejection.js E
U
Promise.onFatalRejection in /lib/decorators/unhandledRejection.js E
U
Promise#inspect in /lib/decorators/inspect.js E

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

This page is for cujojs/when 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.