Proposal

Currently, App#client() never holds a token even when a token is passed to App constructor. This had been intentional as bolt-js used to behave this way.

However, we've revisited it on the bolt-js side and now app.client in a bolt-js app holds a token when it is passed in its constructor. slackapi/bolt-js#948 For this reason, now we can change the behavior of app.client() in the Java SDK too.

Impacts on the existing code

Existing code using app.client() should be using token setter in API method calls. Attaching a token to the client instance does not change the behavior of those existing code. Token as a parameter always overwrites the token passed in MethodsClient constructor.

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

• bolt (Bolt for Java)
• bolt-{sub modules} (Bolt for Java - optional modules)
• slack-api-client (Slack API Clients)
• slack-api-model (Slack API Data Models)
• slack-api-*-kotlin-extension (Kotlin Extensions for Slack API Clients)
• slack-app-backend (The primitive layer of Bolt for Java)

Requirements

Please make sure if this topic is specific to this SDK. For general questions/issues about Slack API platform or its server-side, could you submit questions at https://my.slack.com/help/requests/new instead. 🙇

Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to the those rules.