Repository navigation
fix: handle no args across all bottom sheet dialogs - #1148
Conversation
|
@CodeRabbit review |
✅ Action performedReview finished.
|
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (10)
Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 3 remain after this review. 📝 WalkthroughWalkthroughThe bottom-sheet dialogs now handle missing arguments and guard selected media-browser operations. The contributor guide adds an alternate Retrace path and closes the PR checkout example’s code fence. ChangesBottom-sheet dialog guards
Contributor instructions
Priority: ➖ Normal Estimated code review effort: 2 (Simple) | ~12 minutes Change: Bug fix Merge Risk: ⚪ Minimal · up to The changed dialogs dismiss when required data is missing. No actionable regression was established in the affected lifecycle or song actions; the PR is mergeable after normal checks. 🚥 Pre-merge checks | ✅ 3 | ❌ 2❌ Failed checks (2 warnings)
✅ Passed checks (3 passed)
Full details: Out of Scope Changes checkExplanation The Full details: Docstring CoverageExplanation Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 28 functions across 9 files. (1 skipped: 1 unsupported.)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 Generate unit tests (beta)
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. Comment |
resolves #1145
When SongBottomSheetDialog (or any of the bottom sheet dialogs) is launched or recreated without arguments (or
with a null track object), it now calls:
This immediately dismisses the bottom sheet fragment and returns the user back to the underlying screen
("kicking" them out of the invalid dialog) rather than throwing an IllegalStateException and crashing the
application.
Summary by CodeRabbit