Ankur Oberoi
Ankur Oberoi
### Description Currently, when tests are run within each package, they run within the context of only that package. That means that all file paths in the coverage report start...
### Description Currently when Codecov collects/aggregates coverage reports for a specific change, the reports from several packages collide in a way that makes the aggregations incorrect. For example, both the...
### Description Currently the `Installation` object contains a single `incomingWebhook` property, as an object with several properties. That works when an OAuth flow completes and the installation needs to be...
### Description From the [platform changelog](https://api.slack.com/changelog/2017-09-the-one-about-usernames): > The undocumented approach to mentioning users via the API — — will no longer function after September 12, 2018. Please reference with the...
### Description We've noticed some changes in the RTM message format but have not actively updated the processing of each event in [`eventWrapper`](https://github.com/slackapi/hubot-slack/blob/4351cab45038dd4872254552e214965f959c22e4/src/client.coffee#L324-L381) accordingly. It's possible that some of the...
### Description in order to know anything about a message after it has been sent, there needs to be a way to run a callback after the `chat.postMessage()` method completes....
### Description Azure-based hosting in App Service's Web Apps (formerly known as Websites) per the [official Hubot deployment instructions](https://hubot.github.com/docs/deploying/azure/) is currently broken. ~After some investigation in #283, we don't yet...
### Description in the current implementation, `SlackClient#loadUsers()` will typically be called twice each time Hubot starts up. the first time, immediately. the second time, after the brain's storage connection is...
### Description The built in OAuth is super convenient and great! It fetches the appropriate `Installation` from my `InstallationStore` and uses the tokens in that installation to authorize the incoming...
I'd like to suggest that instead of calling `process.exit()`, we throw an `Error`. As described in [node's documentation for `process.exit()`](https://nodejs.org/api/process.html#process_process_exit_code), using this method is problematic because it disrupts all asynchronous...