Move TODO. field1, field2... -> fields...

api/application-service/application_service.yaml

@@ -321,7 +321,7 @@ paths:
           required: true
           x-example: irc
         - in: query
-          name: field...
+          name: fields...
           type: string
           description: |-
             One or more custom fields that are passed to the application
@@ -446,4 +446,4 @@ paths:
               "errcode": "COM.EXAMPLE.MYAPPSERVICE_NOT_FOUND"
             }
           schema:
-            $ref: ../client-server/definitions/errors/error.yaml
+            $ref: ../client-server/definitions/errors/error.yaml

api/client-server/third_party_lookup.yaml

@@ -129,9 +129,8 @@ paths:
             The name of the protocol.
           required: true
           x-example: irc
-          # TODO: Change to 'explode' after OpenAPI/Swagger v3 update
         - in: query
-          name: field1, field2...
+          name: fields...
           type: string
           description: |-
             One or more custom fields that are passed to the AS to help identify the user.

api/openapi_extensions.md

@@ -8,6 +8,8 @@ parsers should be able to take advantage of the added syntax.
 
 ## Extensible Query Parameters
 
+<!-- TODO: Remove and change instances to 'explode' after OpenAPI/Swagger v3 update -->
+
 If a unknown amount of query parameters can be added to a request, the `name`
 must be `fields...`, with the trailing ellipses representing the possibility
 of more fields.
@@ -18,4 +20,4 @@ Example:
   - in: query
     name: fields...
     type: string
-```
+```