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
At the moment, only the conversation_select which has the filter object. In the slack documentation, it said the filter object also supported in the multi_conversation_select.
As a workaround to bypass this issue, i create a conversation_select block element, and change the element type once it created to be multi_conversation_select, like:
varmodal slack.ModalViewRequest// omitted code to parsed/unmarshal the json kit to be the the view struct// ...block:=modal.Blocks.BlockSet[0].(*slack.SectionBlock)
block.Accessory.SelectElement.Type="multi_conversations_select"modal.Blocks.BlockSet[0] =block
But i think that way is not clean, since we actually can directly create the multi_conversation_select with filter object based on the slack documentation.
I create my own pull request in #1191, please help to review and merge / please help to fix that issue if my PR is not suitable.
Thank you!
The text was updated successfully, but these errors were encountered:
Hi team, currently there is no
filter
field in themulti_conversation_select
block element type like below:slack/block_element.go
Lines 270 to 283 in b4b5a64
At the moment, only the
conversation_select
which has thefilter
object. In the slack documentation, it said thefilter
object also supported in themulti_conversation_select
.As a workaround to bypass this issue, i create a
conversation_select
block element, and change the element type once it created to bemulti_conversation_select
, like:Example json kit template used
But i think that way is not clean, since we actually can directly create the
multi_conversation_select
withfilter
object based on the slack documentation.I create my own pull request in #1191, please help to review and merge / please help to fix that issue if my PR is not suitable.
Thank you!
The text was updated successfully, but these errors were encountered: