Bugfix: properly select all-between when messages were rescheduled afterwards#375
Bugfix: properly select all-between when messages were rescheduled afterwards#375dazewell wants to merge 2 commits into
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (2)
💤 Files with no reviewable changes (1)
📝 WalkthroughSummary by CodeRabbit
WalkthroughThe PR refactors the "select between messages" logic in ChangesSelect Between Messages Refactoring
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ast-grep (0.42.3)TMessagesProj/src/main/java/org/telegram/ui/ChatActivity.javaThanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: 8ab33a2e-4ba6-4893-a361-4af7789b9e71
📒 Files selected for processing (1)
TMessagesProj/src/main/java/org/telegram/ui/ChatActivity.java
|
Fixed in 79d9b3e. Thanks. |
Repro
Expected
All messages are selected: 1, 2, 3, 4
Actual
Only the following messages are selected: 1, 2, 4