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
On my PR for handler-slack-multichannel.rb (see here) I modified the channel composition from the original created by Rob Wilson in his initial commit (99e1baa9) so that the handler accepts both arrays of channels and strings (single channel), which is the standard in the handler-slack.rb.
While discussing about the PR I realized that if we port this support for both strings and arrays to the handler-slack.rb it would be no longer necessary to keep 2 versions of the handler, which have already diverged in some ways (notable example: handling of non-standard status codes in the message composition, which was breaking the execution), making it difficult to maintain both properly.
It also makes it hard to justify to users to have both versions set in their system asking them to use one or the other depending on the scenario.
I think it would be easier to just port this (should be easy) and completely remove handler-slack-multichannel.rb.
The text was updated successfully, but these errors were encountered:
This could be moved over to the slack specific repository, the other RFC made sense in this repo as we are discussing it across all plugins where RFC is specific to slack plugin. The short answer: that sounds like a good idea to me. Please open an issue on the correct repository so we can track the progress
In order to do that we need to:
a deprecation warning to let admins know the change is coming (prs are welcome)
do a minor release (maintainer)
document the differences and call them out in the changelog so people know how to upgrade (prs are welcome)
do a major release (maintainer)
As people should be pinning their versions people should be able to continue to function with the old one for as long as they want.
No worries, I am happy to help. Also if you have questions feel free to hit me up in the community slack. I may not respond right away but I do respond to everything I get.
On my PR for
handler-slack-multichannel.rb
(see here) I modified the channel composition from the original created by Rob Wilson in his initial commit (99e1baa9) so that the handler accepts both arrays of channels and strings (single channel), which is the standard in thehandler-slack.rb
.While discussing about the PR I realized that if we port this support for both strings and arrays to the
handler-slack.rb
it would be no longer necessary to keep 2 versions of the handler, which have already diverged in some ways (notable example: handling of non-standard status codes in the message composition, which was breaking the execution), making it difficult to maintain both properly.It also makes it hard to justify to users to have both versions set in their system asking them to use one or the other depending on the scenario.
I think it would be easier to just port this (should be easy) and completely remove
handler-slack-multichannel.rb
.The text was updated successfully, but these errors were encountered: