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
It seems that the current version latest version (v4.6.0) does not support using of proxy for Incoming Webhooks, unlike Web API Client and RTM API Client. It seems to me that it should be possible to have the same implementation as with Web API and RTM API client, wherein a custom agent as a parameter of the constructor function as such:
This would totally be a great addition. At the moment, the core maintainers don’t see enhancements to IncomingWebhook as a priority, but PRs for this functionality would be happily accepted.
Description
It seems that the current version latest version (v4.6.0) does not support using of proxy for Incoming Webhooks, unlike Web API Client and RTM API Client. It seems to me that it should be possible to have the same implementation as with Web API and RTM API client, wherein a custom agent as a parameter of the constructor function as such:
using tunnel
or using https-proxy-agent
What type of issue is this? (place an
x
in one of the[ ]
)Requirements (place an
x
in each of the[ ]
)The text was updated successfully, but these errors were encountered: