Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Having read a lot of Slack documentation and operated v2.0.0.3 in production for a bit, I now understand that the Slack message attachment field is poorly standardized. None of the fields are required and there are different versions of the attachments api over the years that are all supported in this one field.
To make apps that look at attachments, chance are, you're going to need to look at the raw json value. So I've edited slack-web to try to decode the attachment based on documented schema (and ported from Slack's own open source javascript sdks) but then also pass the raw json value to clients.
Before submitting your PR, check that you've:
@since
declarations to the HaddockAfter submitting your PR:
(unreleased)
on the Changelog