Summary
When developing Slack apps that need to run against non-production API endpoints (e.g. qa.slack.com), developers must manually wire the SLACK_API_URL environment variable into the App constructor via clientOptions.slackApiUrl. It would be useful for Bolt to automatically read SLACK_API_URL from the environment and apply it without requiring template/app-level boilerplate.
Context
The starter template currently requires an explicit code change to support custom API URLs:
Ideally this would be handled at the framework level so every template and app gets it for free.
Proposal
Have Bolt automatically check for SLACK_API_URL in the environment and use it as the default slackApiUrl in client options when present, without requiring explicit configuration in app code.
Summary
When developing Slack apps that need to run against non-production API endpoints (e.g.
qa.slack.com), developers must manually wire theSLACK_API_URLenvironment variable into theAppconstructor viaclientOptions.slackApiUrl. It would be useful for Bolt to automatically readSLACK_API_URLfrom the environment and apply it without requiring template/app-level boilerplate.Context
The starter template currently requires an explicit code change to support custom API URLs:
Ideally this would be handled at the framework level so every template and app gets it for free.
Proposal
Have Bolt automatically check for
SLACK_API_URLin the environment and use it as the defaultslackApiUrlin client options when present, without requiring explicit configuration in app code.