Support all the methods from the API

[davesnx]

Hey @mishk0,

Seems that this module doesn't support all the endpoints available on the API api.slack.com/methods.

What about have some methods defined by a configuration file (often a yaml) that defines all the methods from the API with the parameters and have other "custom" methods implemented directly in JavaScript. Like getGroupById, getChannelById, etc...

We could apart of support all the methods from the API, explain how this slack-api-client add extra value of the raw slack API.

Thanks :D

[mishk0]

Yes. Initially, that module was designed for "sending message" purpose. I was convinced, that adding a new simple wrapper for every API call is redundant. Could you show a code of a method that defined by a configuration file, in order to avoid misunderstandings :)

[davesnx]

yml file is a subset of JSON, it's just define a json file like that:

{
  "methods": [
    {
      "endpoint": "channels:history",
      "type": "GET",
      "parameters": {
          "name": "channel"
      }
    }
  ]
}

and the parse it and assign to the get/post private method from the class.

Sounds good?

[davesnx]

and aswell, we can have the documentation dynamic, just adding jsDoc it will output that on the README. Like swagger.

[mishk0]

Yes, sounds good. Anyway, I don't see a huge advantage over js functions. But... could you do PR? :)

[TheGrandmother]

This feature would be really nice to have but i also don't really see why we shouldn't just use JS functions.

[hydeenoble]

Are we still supporting all methods from the Slack API?

[davesnx]

I'm closing this since there's no activity related to that.
I particularly implemented myself the Slack interface with my App

[hydeenoble]

Hello @davesnx, I currently have a PR (#115) for the "files.upload" method for slack API which I need in an App in am currently working on.

I would be glad if activities related to all other methods in the slack API begins all over again and I am more than ready to help.

Thanks.