No description
  • CoffeeScript 100%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
2015-05-29 15:07:24 -07:00
bin Towards automarking behavior 2014-04-13 22:20:07 -07:00
examples Added null checking to prevent bot from crashing if user name, text or channel cannot be determined. 2015-02-25 12:09:13 -08:00
src Merge pull request #31 from c2gconsulting/master 2015-05-29 15:06:34 -07:00
test getChannelByName now strips hashes 2015-02-04 16:22:57 -08:00
.gitignore Compile coffeescript to javascript for npm 2014-12-14 11:41:20 -08:00
.npmignore Compile coffeescript to javascript for npm 2014-12-14 11:41:20 -08:00
.travis.yml Updating requirements - require node > 0.10.x. 2015-02-17 15:58:06 -08:00
CHANGELOG.md Update changelog 2015-02-25 17:00:50 -08:00
Gruntfile.coffee Removed old javascript example. Replaced with coffeescript example 2015-02-25 12:09:12 -08:00
index.coffee Starting to make objects for all the other classes we will need to get chat running 2014-03-16 22:34:29 -07:00
LICENSE Update copyright statements to use our new legal name 2014-10-26 13:32:09 -07:00
package.json release 1.4.1 2015-05-29 15:07:24 -07:00
README.md Initial commit of a simple example of how to use the slack-client module from Node. 2014-12-24 10:45:29 -08:00

Node.js Slack Client Library

Travis-CI Build Status

Build Status

Description

This is a Slack client library for Node.js. It is intended to expose all of the functionality of Slack's Real Time Messaging API while providing some common abstractions and generally making your life easier, if you want it to.

This code has been built to support our hubot-slack adapter. Most other functionality isn't yet supported, and documentation is minimal, at best. A simple example of how to use this module from Node.js can be found in the examples directory.

Contribute

Here's the most direct way to get your work merged into the project.

  1. Fork the project
  2. Clone down your fork
  3. Create a feature branch
  4. Hack away and add tests, not necessarily in that order
  5. Make sure everything still passes by running tests
  6. If necessary, rebase your commits into logical chunks without errors
  7. Add yourself to package.json as a contributor
  8. Push the branch up to your fork
  9. Send a pull request for your branch

Copyright © Slack Technologies, Inc. MIT License; see LICENSE for further details.

TODOs

  1. Better/any timeouts on initial websocket connection
  2. Better/any timeouts on API calls
  3. Document the connection options, etc
  4. Emit more events around unreads and mentions