-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unknown block type when decoding chat.postMessage
response
#14
Milestone
Comments
{
"ok": true,
"channel": "DKVSHS1HC",
"ts": "1653756786.810519",
"message": {
"bot_id": "BKTND7QN4",
"type": "message",
"text": "Hello World!!",
"user": "UKGA4ARMY",
"ts": "1653756786.810519",
"app_id": "AJ9649K6F",
"team": "T3GV5VB0D",
"bot_profile": {
"id": "BKTND7QN4",
"app_id": "AJ9649K6F",
"name": "Rookie",
"icons": {
"image_36": "https://avatars.slack-edge.com/2019-06-23/673287830948_0affbbb86beca00aa028_36.png",
"image_48": "https://avatars.slack-edge.com/2019-06-23/673287830948_0affbbb86beca00aa028_48.png",
"image_72": "https://avatars.slack-edge.com/2019-06-23/673287830948_0affbbb86beca00aa028_72.png"
},
"deleted": false,
"updated": 1561328910,
"team_id": "T3GV5VB0D"
},
"blocks": [
{
"type": "rich_text",
"block_id": "Zjof6",
"elements": [
{
"type": "rich_text_section",
"elements": [
{
"type": "text",
"text": "Hello World!!"
}
]
}
]
}
]
}
} |
I am a complete rust newb, but what I don't understand is why it is an error. From the documentation, it sounds like serde should ignore json values it is not aware of, unless |
@Leonid99 did you figure out a way around this? |
I went ahead and forked + added a minor patch for the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When doing (event API in socket mode):
I am getting the following error:
The list of variants seems to suggest that there is an unsupported block type (the documentation doesn't list "rich_text" as a possible Block type).
This is happening when I am sending a message to the bot I'm working on from the normal Slack client.
The text was updated successfully, but these errors were encountered: