[Question] Any plans on supplying specifications for the RTM API events?

[Mange]

Description

Is there any plans to supply Swagger specifications for the RTM messages? It would be very useful for SDKs out there to be able to generate code from official specifications instead of scraping the documentation website (which a lot of them are doing right now).

Examples of this happening:

• slack-rs/slack-api-schemas (for slack-rs/slack-api) - Rust API
• slack-ruby/slack-api-ref (for slack-ruby/slack-ruby-client) - Ruby API

What type of issue is this? (place an x in one of the [ ])

• [ ] bug
• [ ] enhancement (feature request)
• [x] question
• [ ] documentation related
• [ ] testing related
• [ ] discussion

Requirements (place an x in each of the [ ])

• [x] I've read and understood the Contributing guidelines and have done my best effort to follow them.
• [ ] I've read and agree to the Code of Conduct.
• [x] I've searched for any related issues and avoided creating a duplicate issue.

[episod]

Hi @Mange! I don't have timing to share about our plans to add JSON schema or OpenAPI 3.0 schemas for the RTM or Events API right now, but it's something we're considering. Most likely we'll target the Events API first, which could have some re-usability for RTM enthusiasts. Swagger/OpenAPI 2.0 aren't well-suited to describing either RTM or Events API unfortunately.

[Mange]

I'm glad to hear it. Thank you. :)

I think plain JSON schema to describe the events would solve the problem for most integrators as they can then generate types, documentation and tests for their respective libraries. Just a tip! :)