You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The differences between chat_postMessage and file_upload_v2 lead to a sometimes frustrating dev experience. For instance, chat_postMessage includes the username parameter, allowing the developer to customize the username.
The file_upload_v2 function has no such parameter, so the bot's name cannot be customized, resulting in Slack threads with messages from the same bot, but named differently (custom username or the default name).
It would be very helpful if one could specify the username when executing file_upload_v2, as can be done for chat_postMessage.
There is also the difference between chat_postMessage and file_upload_v2 in regards to how channels can be specified. chat_postMessage allows channel names, while file_upload_v2 requires channel IDs. If one tries to use a channel name with file_upload_v2, the returned error is "channel not found" instead of a more informative error, such as "channel not found; note: this endpoint requires a channel ID".
Category (place an x in each of the [ ])
slack_sdk.web.WebClient (sync/async) (Web API client)
Hey @nick-youngblut 🙇🏻 This is fantastic feedback, thank you!
From my understanding, these improvements around consistencies are at the Slack API level. We could consider patching them at the SDK level, but it would be a workaround that should be solved on the API.
I've shared your feedback internally with the Slack Platform team and I'm looking to see whether we can take it a step further than just reporting the feedback. So, I'll leave this issue open for a bit in case others would like to chime in!
👋 It looks like this issue has been open for 30 days with no activity. We'll mark this as stale for now, and wait 10 days for an update or for further comment before closing this issue out. If you think this issue needs to be prioritized, please comment to get the thread going again! Maintainers also review issues marked as stale on a regular basis and comment or adjust status if the issue needs to be reprioritized.
Just chiming in to express interest for this behavior, specially allowing the use of channel names ("#channel-name") instead of IDs when uploading files!
The differences between
chat_postMessage
andfile_upload_v2
lead to a sometimes frustrating dev experience. For instance,chat_postMessage
includes theusername
parameter, allowing the developer to customize the username.The
file_upload_v2
function has no such parameter, so the bot's name cannot be customized, resulting in Slack threads with messages from the same bot, but named differently (custom username or the default name).It would be very helpful if one could specify the username when executing
file_upload_v2
, as can be done forchat_postMessage
.There is also the difference between
chat_postMessage
andfile_upload_v2
in regards to how channels can be specified.chat_postMessage
allows channel names, whilefile_upload_v2
requires channel IDs. If one tries to use a channel name withfile_upload_v2
, the returned error is "channel not found" instead of a more informative error, such as "channel not found; note: this endpoint requires a channel ID".Category (place an
x
in each of the[ ]
)Requirements
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.
The text was updated successfully, but these errors were encountered: