Now that SIGs are rebranded as Activities, we can merge DXpedition and Contest into that without it being too weird, and get rid of AlertType #147

static/apidocs/openapi.yml

@@ -14,7 +14,12 @@ info:
     Spothole's source code is located at https://git.ianrenton.com/ian/spothole and the README there provides setup instructions if you would like to run your own copy. A demonstration server of Spothole is located at https://spothole.app. The README also contains some examples of how you could query the API of the demonstration server to integrate the data into your own apps.
 
     ## Changelog
+
+    ### 2.2
     
+    * 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 :)
+
     ### 2.1
     
     * Added AMSAT, EME, DTMBA, FEA, BIWOTA, COTA & PGA SIGs
@@ -952,14 +957,6 @@ components:
         - TOILET
       example: PARK
 
-    AlertType:
-      type: string
-      enum:
-        - XOTA
-        - DXPEDITION
-        - CONTEST
-      example: XOTA
-
     Continent:
       type: string
       enum:
@@ -1489,9 +1486,6 @@ components:
           items:
             $ref: '#/components/schemas/ActivityRef'
           description: Activity references. We allow multiple here for e.g. n-fer activations, unlike ADIF SIG_INFO. Still named "sig_refs" in the API for backwards compatibility.
-        alert_type:
-          description: "The type of alert this is: xOTA, DXpedition, or Contest."
-          $ref: "#/components/schemas/AlertType"
         url:
           type: string
           description: A URL linking to more information about the alert, e.g. DXpedition or contest info.