slackapi / slackapi/node-slack-sdk
conversations.setTopic missing `channel.latest` in returned object
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3.4k
- Forks
- 688
- Avg merge
- 15h 31m
- Merged PRs (30d)
- 27
Description
@slack/bolt version
4.6.0
Your App and Receiver Configuration
e.g. const app = new App({ token: slackToken, socketMode: true, signingSecret: process.env.SLACK_SIGNING_SECRET, appToken: process.env.APP_TOKEN, scopes: [ "app_mentions:read", "channels:history", "channels:read", "chat:write", "commands", "groups:history", "groups:read", "im:history", "im:read", "im:write", "mpim:history", "mpim:write", "reactions:read", "reactions:write", "users.profile:read", "users:read", ], });
Node.js runtime version
v24.11.1
Steps to reproduce:
- Init empty project
- Add app with configurations mentioned above
- Add bot to workspace, create a channel
Call client.conversations.setTopic:
const result = await app.client.conversations.setTopic({ channel: channelId, topic: "some random topic", });
Expected result:
result.channel.latest to not be undefined
Actual result:
.latest is undefined
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the client.conversations.setTopic entry point and reproduce the call with the configuration and versions listed. Trace the returned response and any existing coverage for this method; done means the result exposes channel.latest after the topic update.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100