Support message attachments legacy fields #39
Merged
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.
As documented at https://api.slack.com/reference/messaging/attachments
Some bots that are used at my employer use the legacy attachments formatting instead of blocks so I hacked this in.
This should probably be a separate function and could be refactored to reduce some nesting, but this is what I'm running right now.
The current version is missing support for the following items because I haven't got around to handle images inside messages but it shouldn't be too hard to implement by refactoring
renderImageBlock
a bit:Not sure if this warrants a draft to wait until images are handled or if this can be added as is (after review).