Fixed thinking message deletion

[rangamani54]

• Changed existing logic to use GetThreadReplies for deleting Thinking message after actual AI response.
• Fixes the issue [BUG] Delete thinkingMessage doesn't work #140

Summary by CodeRabbit

• Bug Fixes
  • Improved Slack thread message handling by fetching thread replies directly instead of retrieving general channel history.

[coderabbitai]

Walkthrough

The pull request modifies internal/slack/userFrontend.go to switch from fetching the last 10 messages in a channel using GetConversationHistory to fetching thread replies using GetThreadReplies with a channel ID and thread timestamp. The iteration now processes a slice directly. Deletion logic and error handling for the bot thinking message remain unchanged.

Changes

Cohort / File(s)	Change Summary
Message retrieval refactoring internal/slack/userFrontend.go	Replaced GetConversationHistory API call with GetThreadReplies(channelID, threadTS) for fetching messages. Updated iteration to process returned slice directly instead of Messages collection. Preserved bot thinking message deletion logic and error handling.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Verify that threadTS is correctly passed and available in the calling context
• Confirm that the slice iteration correctly replaces the Messages collection logic
• Ensure the API change from channel history to thread replies is intentional and aligns with the intended behavior

Possibly related PRs

• Add thinkingMessage constant #46: Introduces thinkingMessage constant used in the bot message deletion check within the same file, coordinating with this refactoring of message retrieval logic.

Suggested labels

enhancement

Poem

🐰 Down rabbit holes of threads so deep,
Where conversation secrets sleep,
No need for channel-wide array,
Just thread replies light the way! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The PR title "Fixed thinking message deletion" is directly related to the main change in the changeset. The primary purpose of this PR is to fix the logic for deleting thinking messages by switching from GetConversationHistory to GetThreadReplies, and the title clearly captures this intent. A teammate scanning the repository history would understand that this PR addresses a bug related to thinking message deletion. While the title doesn't include the technical implementation detail (the shift to GetThreadReplies), the instructions acknowledge that titles need not cover every detail of the changeset.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[tuannvm]

thanks @rangamani54