Daniel (dB.) Doubrovkine

These are the days I wish this was a GraphQL interface :( 1. Should we make this future-compatible with additional fields? ``` "matched_queries" : { "foo_query" : { "score": 0.2876821...

> > Should we make this future-compatible with additional fields? > > What additional fields? :) So let's do it? It also makes clear what this numeric value is. >...

So what you're suggesting is deprecating `matched_queries` in 2.x and potentially removing it in 3.0? I like it. We could do this that I think can stand the test of...

Let's make a breaking change for 3.0 in this PR? I feel pretty strongly that we should avoid this problem for future changes here and do: ``` "matched_queries" : {...

@bodgit Are you going to try and contribute an implementation to OpenSearch? PRs welcome!

This is pretty old, but still an issue. Will queue up fixing after #2295 is merged.

@gabifija In slack-ruby-client 2.0 these were set to `nil`, see https://github.com/slack-ruby/slack-ruby-client/blob/master/UPGRADING.md#upgrading-to--200. Your issue is different, the OP is setting these to specific values.

Thanks @ioquatix for bringing this up from Grape and @domenic and @annevk for your comments! Y'all make a ton of sense, even though I think you are too focused on...

I found a lot of NULLs in URLs, https://www.wired.com/2015/11/null/ 🤷

What's the call stack that causes the rate limit? The library that calls `conversations.list` is https://github.com/slack-ruby/slack-ruby-client. That supports pagination. https://github.com/slack-ruby/slack-ruby-client/blob/master/lib/slack/web/api/endpoints/conversations.rb#L242