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.
First of all: I really like your joe-bot and the adapters that come with it.
Thanks for your great work!
However, I ran into a bit of a problem currently with the slack-adapter:
In one of my projects I use your slack adapter inside a custom joe-bot adapter.
This custom joe-bot adapter several custom send methods which used to use the Send()-method of your slack-adapter.
Since I now want to additionally send slack-blocks, when sending messages to slack, I need to be able to hand over a slack blocks message option to the slack API. However this is currently not possible, because the slack API is hidden inside your slack BotAdapter. But with offering a
SendWithSlackOpts(...)
-method, this could become easily available.What I used to do:
What I would like to do:
I wonder whether It would be possible to offer such a
SendWithSlackOpts(...)
-method?Or is there anything speaking against it?