Hi,
I notice that in the web api, search.messages is defined like this:
messages: MethodWithRequiredArgument<SearchMessagesArguments, SearchMessagesResponse>;
And SearchMessagesArguments is defined like this:
export interface SearchMessagesArguments extends TokenOverridable, TraditionalPagingEnabled, Searchable {
}Should it extend CursorPaginationEnabled in addition to TraditionalPagingEnabled? I see that the Slack developer docs list the search.messages method as taking a cursor. But because this only extends TraditionalPagingEnabled, cursors cannot be passed to it.
Packages:
Select all that apply:
Requirements
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.
Hi,
I notice that in the web api,
search.messagesis defined like this:And
SearchMessagesArgumentsis defined like this:Should it extend
CursorPaginationEnabledin addition toTraditionalPagingEnabled? I see that the Slack developer docs list thesearch.messagesmethod as taking acursor. But because this only extendsTraditionalPagingEnabled,cursors cannot be passed to it.Packages:
Select all that apply:
@slack/web-api@slack/rtm-api@slack/webhooks@slack/oauth@slack/socket-mode@slack/typesRequirements
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.