search

netromdk / slacker

Slacker - Easy access to the Slack API and admin of workspaces/teams.
MIT License
14 stars 0 forks source link

Figure out which API methods to implement #40

Closed netromdk closed 6 years ago

netromdk commented 6 years ago

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 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?

0verbyte commented 6 years ago

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

yaes

netromdk commented 6 years ago

I agree that we should soon get v0.1 out the door and make the repo public (finally!) :p

As far as the commands go, [...]

Yeah, that's a good idea. But first we must define the contribution rules and how-to file and better explain things in the README.

netromdk commented 6 years ago

Closing this because we have the commands mentioned and we'll add them as we go.