feat(notifications): make connection-problem sound opt-in - #633
Conversation
The Signal K connection retry and permanent-failure toasts played notification.mp3 on every interruption. The sound now needs notificationConfig.sound.playConnectionSound, which defaults to off and is absent from configs written before this change. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
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 configurationConfiguration used: Repository: halos-org/skip/.coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (7)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughChangesConnection sound preference
Priority: ⬇️ Low Estimated code review effort: 3 (Moderate) | ~20 minutes Change: Feature Sequence Diagram(s)sequenceDiagram
participant SettingsService
participant AppComponent
participant ToastService
SettingsService->>AppComponent: Provide playConnectionSound
AppComponent->>AppComponent: Check setting and bootstrap readiness
AppComponent->>ToastService: Show connection-status toast with sound flag
Merge Risk: ⚪ Minimal · up to This makes Signal K connection sounds opt-in while preserving silent behavior for existing configurations; no merge-blocking risk is currently established. 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✨ Finishing Touches📝 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 |
Every interruption of the Signal K server connection played
assets/notification.mp3. On a boat with a flaky link that is a chime every few seconds, and there was no way to turn it off short of disabling all notification audio.The retry, permanent-failure and unknown-state connection toasts are now silent unless the new
notificationConfig.sound.playConnectionSoundoption is on. It defaults to false, and configs written before this change lack the field, which reads as off — so no migration and no version bump (VERSIONis already at 1.5.0 against the v1.4.1 stable release, so the cycle is open).The checkbox sits at the top level of Settings → Notifications, next to "Disable audio", rather than inside the Audio expansion panel. That panel is disabled by
disableNotifications, which governs Signal K notification states; a connection toast is not one of those, so burying the option there would make it unreachable for a user who has notifications off.Tests cover the default-silent path, the opted-in path, the bootstrap suppression that still wins over the opt-in, and a stored config that predates the field.
🤖 Generated with Claude Code
Play a sound on Signal K connection problemsto Notifications settings.notificationConfig.sound.playConnectionSoundtofalse, including for older stored configurations.