[NOMERGE] feat: openapi migration progress

content-management.yaml

@@ -86,69 +86,6 @@ paths:
                     success: true
         '401':
           $ref: '#/components/responses/authorizationError'  
-  /api/v1/emoji-custom.create:
-    post:
-      tags:
-        - Custom Emoji
-      summary: Create an Emoji
-      description: |
-        Upload a custom emoji to the workspace. Make sure that you have configured the storage system. For details, refer to the [Manage Custom Sounds and Emojis](https://docs.rocket.chat/docs/manage-custom-sounds-and-emojis) document.
-
-        Permission required: `manage-emoji`
-
-        ### Changelog
-        | Version      | Description | 
-        | ---------------- | ------------|
-        |0.74.0            | Added       |
-      operationId: post-api-v1-emoji-custom.create
-      parameters:
-        - $ref: '#/components/parameters/Auth-Token'
-        - $ref: '#/components/parameters/UserId'
-      requestBody:
-        content:
-          multipart/form-data:
-            schema:
-              type: object
-              required:
-                - emoji
-                - name
-              properties:
-                emoji:
-                  type: string
-                  description: The image file to use as the new custom emoji.
-                  format: binary
-                name:
-                  type: string
-                  description: The name of the new custom emoji.
-                aliases:
-                  type: string
-                  description: The alias of the new custom emoji.
-      responses:
-        '200':
-          $ref: '#/components/responses/trueSuccess'
-        '400':
-          description: Bad Request
-          content:
-            application/json:
-              schema:
-                type: object
-                properties:
-                  success:
-                    type: boolean
-                  error:
-                    type: string
-              examples:
-                Example 1:
-                  value:
-                    success: false
-                    error: Missing Content-Type
-                Example 2:
-                  value:
-                    success: false
-                    error: '[No file uploaded]'
-                    errorType: No file uploaded
-        '401':
-          $ref: '#/components/responses/authorizationError'  
   /api/v1/emoji-custom.delete:
     post:
       tags:
@@ -456,90 +393,6 @@ paths:
                     success: true
         '401':
           $ref: '#/components/responses/authorizationError'  
-  /api/v1/custom-user-status.list:
-    get:
-      tags:
-        - Custom User Status
-      summary: List Custom User Status
-      description: |-
-        Lists all available custom user's status.
-
-        ### Changelog
-        | Version      | Description | 
-        | ---------------- | ------------|
-        |7.0.0           | Added `name` and `_id` query parameters for filtering.      |
-        |2.4.0            | Added       |
-      operationId: get-api-v1-custom-user-status.list
-      parameters:
-        - $ref: '#/components/parameters/Auth-Token'
-        - $ref: '#/components/parameters/UserId'
-        - name: name
-          in: query
-          description: |-
-            Filter list by the name of the custom status.
-          schema:
-            type: string
-          example: lunch
-        - name: _id
-          in: query
-          description: |-
-            Filter list by the _id of the custom status.
-          schema:
-            type: string
-          example: 6731e2ce3b74d3c57d334d0f
-        - $ref: '#/components/parameters/count'
-        - $ref: '#/components/parameters/offset'
-        - schema: {}
-          in: query
-          name: sort
-          description: |-
-           Sort the order of custom user status in ascending (`1`) or descending (`-1`) order. The options are:
-            * `name`: Sort by name. For example, `sort={"name": 1}` (default) or `sort={"name": -1}`.
-            * `statusType`: Sort by status type. For example, `sort={"statusType": 1}` or sort=`{"statusType": -1}`.
-            * You can also sort using both parameters. For example, `sort={"name": 1, "statusType": -1}`.
-      responses:
-        '200':
-          description: OK
-          content:
-            application/json:
-              schema:
-                type: object
-                properties:
-                  statuses:
-                    type: array
-                    items:
-                      type: object
-                      properties:
-                        _id:
-                          type: string
-                        name:
-                          type: string
-                        statusType:
-                          type: string
-                        _updatedAt:
-                          type: string
-                  count:
-                    type: integer
-                  offset:
-                    type: integer
-                  total:
-                    type: integer
-                  success:
-                    type: boolean
-              examples:
-                Success Example:
-                  value:
-                    statuses:
-                      - _id: 63f61be0b000b6b6d86704c8
-                        name: brb
-                        statusType: away
-                        _updatedAt: '2023-02-22T13:42:56.811Z'
-                    count: 1
-                    offset: 0
-                    total: 1
-                    success: true
-        '401':
-          $ref: '#/components/responses/authorizationError'
   /api/v1/custom-user-status.create:
     post:
       tags:

integrations.yaml

@@ -1603,8 +1603,6 @@ paths:
                       method: deleteOAuthApp
 tags:
   - name: Integration
-  - name: OAuth Apps
-  - name: WebDAV
 components:
   parameters:
     offset: