darkhelm/notifications-api
1
0
Fork 0
mirror of https://github.com/GSA/notifications-api.git synced 2026-09-11 18:38:14 -04:00
Code Issues Packages Projects Releases Wiki Activity
8,145 Commits 122 Branches 63 Tags
update-email-status-description
Commit Graph
3 Commits
Author SHA1 Message Date
Chris Hill-Scott 0bb671df45 Validate content length on broadcast API 
The maximum content count of a broadcast varies depending on its
encoding, so we can’t simply validate it against a schema. This commit
moves to using the validation from `notifications-utils`, and raising a
custom error response.
 2021-02-16 09:30:40 +00:00
Chris Hill-Scott e8a79f5413 Don’t accept cancel or update via broadcast API 
We don’t support these methods at the moment. Instead we were just
ignoring the `msgType` field, so issuing one of these commands would
cause a new alert to be broadcast 🙃

We might want to support `Cancel` in the future, but for now let’s
reject anything that isn’t `Alert` (CAP terminology for the initial
broadcast).
 2021-02-15 09:32:33 +00:00
Chris Hill-Scott 7530408a21 Validate broadcast against schema 
This commit adds a JSONSchema which can validate the fields in an API
call to create a broadcast. It takes the CAP XML schema as a starting
point.
 2021-01-26 16:24:44 +00:00