Daniel (dB.) Doubrovkine
Daniel (dB.) Doubrovkine
Should we close this @jmanian ?
Now that https://github.com/dblock/slack-ruby-client/pull/53 introduces minimal expectations around Web api endpoints we could go further. With specs we want to ensure that we didn't break anything accidentally, so I imagine generating...
Not sure. I wouldn't test the Slack API implementation :)
@accessd Makes sense. I wouldn't spend too much time on this. Tests for generated code are important only for the sake of ensuring that we "see" API changes. When someone...
Please help debug! https://samsaffron.com/archive/2015/03/31/debugging-memory-leaks-in-ruby is a decent start.
@zenmatt Did you get a chance to look into it at all?
Also https://github.com/slack-ruby/slack-ruby-client/issues/230
Thanks for hunting it down @schinery. I still want a PR here that ignores those warnings and where tests pass.
We're back to green in #411, but the issue here is still valid: there are tests that fail with a false positive if some gem prints out deprecation warnings. It's...
Note https://twitter.com/jerrydantonio/status/727146124901912578?cn=cmVwbHk%3D&refsrc=email.