websocket-client

Usually, next_cursor in an API response exists under response_metadata property. However, only admin.conversations.search API method's response has it at the top level: https://github.com/slackapi/java-slack-sdk/blob/main/slack-api-client/src/main/java/com/slack/api/methods/response/admin/conversations/AdminConversationsSearchResponse.java#L19

Due to this inconsistency, this part in this Py

Description

Node.js 16 is now available.
https://nodejs.medium.com/node-js-16-available-now-7f5099a97e70

We can start testing with the runtime.
https://github.com/slackapi/node-slack-sdk/blob/d4e89b7270c07423656f7a6fea52782345aa9254/.github/workflows/ci-build.yml#L20

What type of issue is this? (place an x in one of the [ ])

• bug
• enhancement (feature request)

Description

The code snippet in the "Acknowledging events" document should be updated to be compatible with the latest platform features (say, block_actions / block_suggestions etc.).

In bolt-python document, we have a block_suggestion code example: https://slack.dev/bolt-python/concepts#acknowledge Perhaps, something similar would be mor

Even though this isn't super critical, this might help with addressing https://stackoverflow.com/questions/57938081/blazor-preview-9-mono-wasm-memory-access-out-of-bounds-max-string-size-for-dotn

The existing users.info integration tests do not verify the patterns with stranger users, which are the ones in a different org/workspace connected through Slack Connect.

For this reason, the generated JSON data does not have the property is_stranger: boolean (the property can exist only when a user is a stranger as of today): https://github.com/slackapi/java-slack-sdk/blob/main/json-logs/sa

LibLog is deprecated now : damianh/LibLog#270
We should clean related code.