-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace slack-utils with the slack package #71
Comments
Can you post the link to the slack package you're talking about? |
captn3m0/slack-utils on GitHub, slack-utils on NPM.
… On 07-Jun-2019, at 22:13, Vaibhav ***@***.***> wrote:
Can you link me to the slack package you're talking about?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Yeah... So I was asking about the package we want to replace slack-utils with. |
Sorry, was on mobile. https://www.npmjs.com/package/slack seems to support everything |
Thanks! I'll take a look at it :) |
@vrongmeal Any update on this? |
Hi! Sorry I've been a bit busy. Totally forgot about this. I'll ask someone else if anyone is interested in changing the dependency. |
Please do. I'm planning to delete the npm package by month end (31st July) |
@vrongmeal Is someone picking this up? |
Yeah. @ayanchoudhary has taken this up. |
The
slack-utils
package was written when there weren't many good clients for Slack available. However:I've been trying to do a new release, but mocha is causing some issues with tests that I don't want to bypass: sdslabs/slack-utils#7
But even then, this would be a stop-gap measure, since
slack-utils
relies on Slack Legacy Tokens and not the new API. Using the new API would also give Jinora some super-powers like supporting multiple organizations easily with one-click installs.The text was updated successfully, but these errors were encountered: