slack-rs-api
slack-rs-api copied to clipboard
slack-rs
Rust interface for the Slack Web API
`slack-rs-api` not supporting `tokio` >1.0 is becoming more and more of an issue since other dependencies are moving forward. This PR updates `tokio` and `reqwest` to their current versions.
The version of `reqwest` used by this crate is quite old, and depends on `tokio` 0.2, which is also old. Both old versions of reqwest and tokio have potential vulnerabilities...
Slack [introduced](https://api.slack.com/messaging/attachments-to-blocks) the new blocks API and deprecated attachments in early 2019. Add a `blocks` field to `slack_api::chat::PostMessageRequest`, and pass it to [chat.postMessage](https://api.slack.com/methods/chat.postMessage).
Support the [files.upload](https://api.slack.com/methods/files.upload) api method.
https://api.slack.com/changelog/2020-11-no-more-tokens-in-querystrings-for-newly-created-apps Indeed, I can use the same token to send a message if I put the token in the header but this crate wants to put it in the query...
Ref.: https://api.slack.com/methods/im.open
PR for #99 This is the first step for migrating to the openapi spec at https://api.slack.com/specs/openapi/v2/slack_web.json. From this brief first look, I guess that this will be a breaking change....
Just reading through this but looks like they finally got round to it https://medium.com/slack-developer-blog/standard-practice-slack-web-openapi-spec-daaad18c7f8
In the examples you're referring to [legacy tokens](https://api.slack.com/legacy/custom-integrations/legacy-tokens), however these cannot be created anymore. I there an alternative?
