You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The files.list has been implemented but we should probably also get files.info and files.delete.
We also have the emoji.list in script form that we need to convert into a command.
We should actually use api.test whenever we start slacker to test if the Slack API is online and also to tell the user if the internet is not working or similar. This could also be made available as the command "api.test" with aliases "t" and "test" (or maybe without those aliases because of auth.test?).
Whenever a workspace is made active we should query auth.test with the token to test whether it is correct or not. Also do on startup. And in --init whenever a token is entered to try to make sure the user cannot type something that is wrong.
It would probably make sense to implement chat.postMessage so that the users can post messages to channels, but that also requires that we can query and get the ID of a channel by name, like "#general" => "C8VL0UBS5" for our workspace. We can list channels using channels.list.
What do you think, @voidpirate?
The text was updated successfully, but these errors were encountered:
I agree that we should check if the API is online on slacker startup and do auth check between workspace switches.
As far as the commands go, I think as long as we get slacker in a useful state we can release, then just start adding other commands as we go. Perhaps we can create an issue for the API method and tag it "Good first issue" so that might inspire other contributors.
It would probably make sense to implement chat.postMessage
For milestone v0.1, we need to figure out which API methods to include from: https://api.slack.com/methods
The
files.list
has been implemented but we should probably also getfiles.info
andfiles.delete
.We also have the
emoji.list
in script form that we need to convert into a command.We should actually use
api.test
whenever we start slacker to test if the Slack API is online and also to tell the user if the internet is not working or similar. This could also be made available as the command "api.test" with aliases "t" and "test" (or maybe without those aliases because ofauth.test
?).Whenever a workspace is made active we should query
auth.test
with the token to test whether it is correct or not. Also do on startup. And in--init
whenever a token is entered to try to make sure the user cannot type something that is wrong.It would probably make sense to implement
chat.postMessage
so that the users can post messages to channels, but that also requires that we can query and get the ID of a channel by name, like "#general" => "C8VL0UBS5" for our workspace. We can list channels usingchannels.list
.What do you think, @voidpirate?
The text was updated successfully, but these errors were encountered: