Add metadata to response_url params

[ducminh-phan]

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

	type ChatPostMessageArgumentsKnownKeys =
	| 'token'
	| 'channel'
	| 'text'
	| 'as_user'
	| 'attachments'
	| 'blocks'
	| 'icon_emoji'
	| 'icon_url'
	| 'link_names'
	| 'mrkdwn'
	| 'parse'
	| 'reply_broadcast'
	| 'thread_ts'
	| 'unfurl_links'
	| 'unfurl_media'
	| 'username';

Expected result:

There should be the key metadata as it seems to be supported. I have tested and metadata is sent successfully.

Actual result:

There is no key metadata

[seratch]

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.

[Joebayld]

I'm having an issue since this fix. It appears it's now requiring metadata to be in the response when it should be optional.

[gfpacheco]

@seratch any updates on this? I'm facing the same issue as @Joebayld

[seratch]

@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.

[gfpacheco]

@seratch you're right! After deleting node_modules and yarn.lock, and running yarn install again the error dissapeared