Kazuhiro Sera

Thanks for bringing a great topic to discuss! >One possible solution is to update the interface for Installation so that the incomingWebhook property becomes incomingWebhooks, which contains an array of...

>But now I'm realizing that determining which authorization info is not that simple. We can't even assume it's the latest installation. In the case of bot tokens, this is quite...

The reference implementation of installation management in the Node SDK does not support multiple installations with incoming webhooks yet. My recommendation is to have historical data for all the installations...

@NoNameProvided Thanks for taking the time to report this issue. You are right that this is a bug affecting TypeScript users.

Hi @kaandok, thanks for writing in. I don't think that this project will add such a customization at least in the short term. If you need this right now, I...

Thanks again for your time and interest here. Unfortunately, we are not planning to take any actions at least in the short term. Let us close this issue now.

Hi @75asa, thanks for writing in! >I know bolt-js is a wrapped version of express, Just to make it clear, this (being Express.js based) used to be true (in v2.x)...

My personal projects support NestJS and Fastify. If you are still looking for a solution for this, take a look at them: * https://github.com/seratch/slack-bolt-extensions/tree/main/packages/bolt-fastify * https://github.com/seratch/slack-bolt-extensions/tree/main/nestjs-example Since bolt-js project does...

Hi @captainsham, thanks for asking the question. >It appears that the conversation context is stored for an entire channel. Is this correct? Yes, it is. >If so, is there any...

Since we've already provided answers to the questions here, let us close this issue now. Whenever you have anything further to discuss, please feel free to write in or create...