Repository navigation
Add metadata to response_url params #1819
Description
Activity
- addedbugM-T: confirmed bug report. Issues are confirmed when the reproduction steps are documentedM-T: confirmed bug report. Issues are confirmed when the reproduction steps are documentedand removed
on May 1, 2023 - changed the title
[-](Set a clear title describing the issue)[/-][+]Add metadata to response_url params[/+]on May 1, 2023 Hi @ducminh-phan, thanks for taking the time to report this issue! You're right that metadata parameter must be allowed for response_url requests. We will resolve this issue in the next release.
Reacted by Duc-Minh Phan- added a commit that references this issue
on May 1, 2023 @gfpacheco @Joebayld Could you help me figure out how to reproduce the issue you've observed?
I've never experienced the type errors in TS:

One possibility is that some of your
@slack/prefixed packages could be quite old and that might cause unexpected type resolution (if that's that case, the minimum requried versions of underlying packages need to be improved). Please check the dependencies and try the latest versions for all of them.@seratch you're right! After deleting
node_modulesandyarn.lock, and runningyarn installagain the error dissapeared

Reproducible in:
The Slack SDK version
@slack/bolt@3.13.0
Node.js runtime version
v16.14.0
OS info
N/A
Steps to reproduce:
bolt-js/src/types/utilities.ts
Lines 5 to 21 in 261030d
Expected result:
There should be the key
metadataas it seems to be supported. I have tested andmetadatais sent successfully.Actual result:
There is no key
metadata