Draft
Conversation
Add well-known notification branches for DSC categories to separate externally received alerts from own-vessel alarm conditions. - Add dscBranch definition in notifications.json with nature-of-distress sub-paths (fire, mob, sinking, etc.) plus undesignated and epirb - Add distress, urgency, safety as well-known names in vessel, sar, aircraft, and aton schemas - Update notificationBranch regex to reserve new names - Document DSC notification paths in notifications.md - Add test data for distress, urgency, safety, and multiple distress
herostrat
force-pushed
the
feat/dsc-notification-paths
branch
from
5d177a4 to
3531fb6
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
For the RFC see #673