Update documentation and add mocha tests #2
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks again! I'll publish to npm shortly. I wouldn't mind hooking this up to travis but I haven't gotten to what that involves yet. So far I've just signed in with my github account at travis-ci.org |
rickbergfalk
added a commit
that referenced
this pull request
Sep 11, 2014
Update documentation and add mocha tests
|
Update has been published to npm under version 1.0.0! I also went ahead and added you as a collaborator in the package.json. Would it be okay if I just went ahead and added you to the git repository as well? |
|
Sure. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updates the documentation to include async usage. Adds mocha for testing.
I went bare-bones on the testing, but I can add a lot more if you have (for example) a travis account and/or a codeclimate account (both are free incidentally).
Any chance you can publish these changes on npm as a new version?