Restrict the activities that we display on the alerts page's filters to just ones that can actually be in alerts #147

static/apidocs/openapi.yml

@@ -20,6 +20,7 @@ info:
     * Renamed AMSAT SIG to "Satellite" as AMSAT is a specific organisation not just a general term for satellite QSOs
     * Removed `alert_type` from alert data. Contest, DXpedition and Satellite alerts now give those values in `sig` instead, alongside the existing outdoor activity programmes. Teeeeechnically a breaking change but AlertType is so new I doubt anyone is using it yet, so slipped this one in anyway. Sorry :)
     * Added QRP, RaDAR Rally, /AM and /MM activities
+    * Added `has_refs` and `alerts_possible` to Activity data
 
     ### 2.1
     
@@ -1604,6 +1605,15 @@ components:
             specific event (e.g. MOTA). Generally for Spothole's own internal use, clients probably won't need this.
             Used to group them in the web UI. Still named "sig_type" in the API for backwards compatibility.
           $ref: "#/components/schemas/ActivityType"
+        has_refs:
+          type: boolean
+          description: >
+            Whether this activity has a fixed set of references (e.g. parks, summits) with an ID that gets
+            "activated", as opposed to activities like Contest or DXpedition which don't.
+        ref_type:
+          description: >
+            The type of reference that gets activated for this activity, e.g. Park or Summit.
+          $ref: "#/components/schemas/ActivityRefType"
         comment_names:
           type: array
           description: >
@@ -1639,6 +1649,11 @@ components:
             Flag emoji, if this activity is specific to a country or region. If null, this activity is treated as
             worldwide.
           example: "🇺🇳"
+        alerts_possible:
+          type: boolean
+          description: >
+            Whether alerts can ever have this activity. While Spothole can assign any activity from spot comments, there
+            are only a limited set that can ever crop up in alerts, because we don't parse general comments for alerts.
 
     SolarConditions:
       type: object