Refactor alert metadata and add an alert metadata page #1468
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.
What does this PR do? 🛠️
This PR changes how we manage metadata about our alerts to be a little more explicit about how they are prioritized against each other, what kind of hazard they are (land, hazard, etc.), and their broader subcategories (we invented this grouping; it's currently
warning
,watch
, andother
– we use it for color keying).While I was in here, I added a page at
/info/alerts
that shows a table of this information. Now we can see all of the alert types we know about, how we prioritize them, what we think they are, etc.https://weathergov-greg.app.cloud.gov/info/alerts
closes #1407