box / box-openapi Goto Github PK

View Code? Open in Web Editor NEW

92.0 92.0 93.0 66.4 MB

OpenAPI 3.0 Specification for the Box APIs

Home Page: https://developer.box.com

License: Apache License 2.0

JavaScript 72.94% HTML 20.06% Dockerfile 7.00%

api box openapi specification swagger

box-openapi's People

Stargazers

Watchers

Forkers

dncarley aambekar-box stefb965 jtoelke casamarco mikeralphson holbrookab fumengyao5544 ramanpalikala lheritage jared-jackson herrliber nmmascia preciselyalyss bodawei band-aid jcleblanc axcessit doanderson gauravatappdirect eric-dinh aiko-k akhor93 hilary gbhoot ctuckz virenderg pjsimon alexlitvinenko rquintin andrewsomething gliubox mauro-sturaro kinlane mitquinn ssassj frogzsj alicegong bsannicolas diegolopez266 marzelinger leftxs jeffki11er michaelclasby0 mwwoda jonyango mohdsk2 mhagmajer bhushan-khadpe antusus fukihasegawa auslaner becastha owardly oliver-jones peteraritchie 500apps-varshini isabella232 marierogers 05bmckay paroxyzm phucnv9985 shurrey slmpire saver3011 raghumurthy-jayandran bryancross bszwarc ctomek uki-tanaka csamitbagrecha gaurao29 soe-youngs smerrill726 qingliaowu himanshung056 nishantpostman lukaszsocha2 ansi2u nishant-test arjankowski congminh1254 boxakorolcz wsocha rutvik-gs srinivaskini barduinor

box-openapi's Issues

Missing if-match header for copy file

Description of the issue

The definition for post_files_id_copy seems to lack the header parameter if-match. This is supposedly required to copy a file to a destination where the target already exists.

Current content

    "/files/{file_id}/copy": {
      "post": {
        "operationId": "post_files_id_copy",
        "summary": "Copy file",
        "description": "Creates a copy of a file.",
        "tags": [
          "Files"
        ],
        "x-box-tag": "files",
        "x-box-enable-explorer": true,
        "x-box-sanitized": true,
        "parameters": [
          {
            "name": "file_id",
            "description": "The unique identifier that represent a file.\n\nThe ID for any file can be determined\nby visiting a file in the web application\nand copying the ID from the URL. For example,\nfor the URL `https://*.app.box.com/files/123`\nthe `file_id` is `123`.",
            "example": "12345",
            "in": "path",
            "required": true,
            "schema": {
              "type": "string"
            }
          },
          {
            "name": "fields",
            "description": "A comma-separated list of attributes to include in the\nresponse. This can be used to request fields that are\nnot normally returned in a standard response.\n\nBe aware that specifying this parameter will have the\neffect that none of the standard fields are returned in\nthe response unless explicitly specified, instead only\nfields for the mini representation are returned, additional\nto the fields requested.",
            "in": "query",
            "example": [
              "id",
              "type",
              "name"
            ],
            "required": false,
            "explode": false,
            "schema": {
              "type": "array",
              "items": {
                "type": "string"
              }
            }
          }
        ],
        "requestBody": {
          "content": {
            "application/json": {
              "schema": {
                "type": "object",
                "required": [
                  "parent"
                ],
                "nullable": false,
                "properties": {
                  "name": {
                    "type": "string",
                    "description": "An optional new name for the copied file.\n\nThere are some restrictions to the file name. Names containing\nnon-printable ASCII characters, forward and backward slashes\n(`/`, `\\`), and protected names like `.` and `..` are\nautomatically sanitized by removing the non-allowed\ncharacters.",
                    "example": "FileCopy.txt",
                    "maxLength": 255
                  },
                  "version": {
                    "type": "string",
                    "description": "An optional ID of the specific file version to copy.",
                    "example": "0"
                  },
                  "parent": {
                    "type": "object",
                    "description": "The destination folder to copy the file to.",
                    "required": [
                      "id"
                    ],
                    "properties": {
                      "id": {
                        "type": "string",
                        "description": "The ID of folder to copy the file to.",
                        "example": "0"
                      }
                    }
                  }
                }
              }
            }
          }
        },
        "responses": {
          "201": {
            "description": "Returns a new file object representing the copied file.\n\nNot all available fields are returned by default. Use the\n[fields](#param-fields) query parameter to explicitly request\nany specific fields.",
            "content": {
              "application/json": {
                "schema": {
                  "$ref": "#/components/schemas/File"
                }
              }
            }
          },
          "304": {
            "description": "Returns an empty response when the `If-None-Match` header matches\nthe current `etag` value of the file. This indicates that the file\nhas not changed since it was last requested."
          },
          "400": {
            "description": "Returns an error if some of the parameters are missing or\nnot valid.\n\n* `bad_request` when a parameter is missing.",
            "content": {
              "application/json": {
                "schema": {
                  "$ref": "#/components/schemas/ClientError"
                }
              }
            }
          },
          "404": {
            "description": "Returns an error if either the source file or the destination\nfolder could not be found, or the authenticated user does not\nhave access to either.\n\n* `not_found` when the authenticated user does not have access\n  to the source file or the destination folder",
            "content": {
              "application/json": {
                "schema": {
                  "$ref": "#/components/schemas/ClientError"
                }
              }
            }
          },
          "409": {
            "description": "* `operation_blocked_temporary`: Returned if either of the destination\n  or source folders is locked due to another move, copy, delete or\n  restore operation in process.\n\n  The operation can be retried at a later point.\n\n* `item_name_in_use` when a folder with the same name already\n  exists.",
            "content": {
              "application/json": {
                "schema": {
                  "$ref": "#/components/schemas/ClientError"
                }
              }
            }
          },
          "default": {
            "description": "An unexpected client error.",
            "content": {
              "application/json": {
                "schema": {
                  "$ref": "#/components/schemas/ClientError"
                }
              }
            }
          }
        }
      }
    }

Expected content

Add header definition like

          {
            "name": "if-match",
            "description": "Ensures this item hasn't recently changed before\nmaking changes.\n\nPass in the item's last observed `etag` value\ninto this header and the endpoint will fail\nwith a `412 Precondition Failed` if it\nhas changed since.",
            "in": "header",
            "required": false,
            "example": "1",
            "schema": {
              "type": "string"
            }
          }

Examples in generated documentation don't work

Generated client library for the upload API using swagger against C# language and framework version .NET 3.5.

Created app and API key in Box dev console

Used code sample in FileUploadApi.md

using System;
using System.Diagnostics;
using IC.He.Sdk.Box.Upload.Api;
using IC.He.Sdk.Box.Upload.Client;
using IC.He.Sdk.Box.Upload.Model;

namespace Example
{
    public class UploadFileExample
    {
        public void main()
        {
            // Configure OAuth2 access token for authorization: OAuth2Security
            Configuration.Default.AccessToken = "YOUR_ACCESS_TOKEN";

            var apiInstance = new FileUploadApi();
            var file = new System.IO.Stream(); // System.IO.Stream | File to upload
            string attributes = "{\"name\": \"10KB.pdf\", \"parent\": { \"id\": \"0\" } }";

            try
            {
                // Upload File
                FileList result = apiInstance.UploadFile(file, attributes);
                Debug.WriteLine(result);
            }
            catch (Exception e)
            {
                Debug.Print("Exception when calling FileUploadApi.UploadFile: " + e.Message );
            }
        }
    }
}

Specified attributes according to the documentation: https://developer.box.com/v2.0/reference#upload-a-file

Received the following response when uploading using the API:

HTTP/1.1 408 Request body incomplete
Date: Tue, 12 Sep 2017 19:38:03 GMT
Content-Type: text/html; charset=UTF-8
Connection: close
Cache-Control: no-cache, must-revalidate
Timestamp: 15:38:03.369

The request body did not contain the specified number of bytes. Got 155, expected 206

Here is the raw request:

POST https://upload.box.com/api/2.0/files/content HTTP/1.1
Accept: application/json
Authorization: Bearer {MY_APP_TOKEN_HERE}
User-Agent: Swagger-Codegen/1.0.0/csharp
Content-Type: multipart/form-data; boundary=-----------------------------28947758029299
Host: upload.box.com
Content-Length: 206
Accept-Encoding: gzip, deflate
Connection: Keep-Alive

Missing pagination fields

Looks like some of the endpoints with pagination are missing the limit/offset fields. I'm going to try submitting a pull request fixing this

Event Resource - Source - Returns File Resource rather than Event Source

Description of the issue

So the documentation says the Event Resource source field will be a User | Event source resource. But it seems like its never returning an Event source, but rather its returning a User|File|Folder.

I am expecting an object with this values: https://developer.box.com/reference/resources/event-source/

But what I am seeing looks like a File Resource. (which is leading me to believe this would be a Folder resource as well)

array(23) { 'type' => string(4) "file" 'id' => string(12) "789214426768" 'file_version' => array(3) { 'type' => string(12) "file_version" 'id' => string(12) "843545438368" 'sha1' => string(40) "cfdbc6607b7edab16f9efbd08d8cd15a9dfe48b0" } 'sequence_id' => string(1) "0" 'etag' => string(1) "0" 'sha1' => string(40) "cfdbc6607b7edab16f9efbd08d8cd15a9dfe48b0" 'name' => string(5) "Roger" 'description' => string(0) "" 'size' => int(12) 'path_collection' => array(2) { 'total_count' => int(1) 'entries' => array(1) { [0] => array(5) { ... } } } 'created_at' => string(25) "2021-03-19T17:44:12-07:00" 'modified_at' => string(25) "2021-03-19T17:44:12-07:00" 'trashed_at' => NULL 'purged_at' => NULL 'content_created_at' => string(25) "2021-03-19T17:44:11-07:00" 'content_modified_at' => string(25) "2021-03-19T17:44:11-07:00" 'created_by' => array(4) { 'type' => string(4) "user" 'id' => string(11) "14742537355" 'name' => string(15) "ComposerPackage" 'login' => string(51) "Removed.com" } 'modified_by' => array(4) { 'type' => string(4) "user" 'id' => string(11) "14742537355" 'name' => string(15) "ComposerPackage" 'login' => string(51) "[email protected]" } 'owned_by' => array(4) { 'type' => string(4) "user" 'id' => string(11) "14742537355" 'name' => string(15) "ComposerPackage" 'login' => string(51) "[email protected]" } 'shared_link' => NULL 'parent' => array(5) { 'type' => string(6) "folder" 'id' => string(1) "0" 'sequence_id' => NULL 'etag' => NULL 'name' => string(9) "All Files" } 'item_status' => string(6) "active" 'synced' => bool(true) }

Current content

Event > source - returns User|Event source

Expected content

Event > source - returns User|File|Folder

Wrong error message being returned with query is missing from request

Description of the issue

When using the search api: https://developer.box.com/reference/get-search/

"query" is a required field. #341

But also the error message for this field missing is incorrect. The message returned is:

{
    "type": "error",
    "status": 400,
    "code": "bad_request",
    "context_info": {
        "errors": [
            {
                "reason": "missing_parameter",
                "name": "to_search",
                "message": "'to_search' is required"
            }
        ]
    },
    "help_url": "http:\/\/developers.box.com\/docs\/#errors",
    "message": "Bad Request",
    "request_id": "..."
}

Notice to the returned field is to_search

The correct field should be query

Current content

{
    "type": "error",
    "status": 400,
    "code": "bad_request",
    "context_info": {
        "errors": [
            {
                "reason": "missing_parameter",
                "name": "to_search",
                "message": "'to_search' is required"
            }
        ]
    },
    "help_url": "http:\/\/developers.box.com\/docs\/#errors",
    "message": "Bad Request",
    "request_id": "..."
}

Expected content

{
    "type": "error",
    "status": 400,
    "code": "bad_request",
    "context_info": {
        "errors": [
            {
                "reason": "missing_parameter",
                "name": "query",
                "message": "'query' is required"
            }
        ]
    },
    "help_url": "http:\/\/developers.box.com\/docs\/#errors",
    "message": "Bad Request",
    "request_id": "..."
}

fields example has a spelling mistake

Description of the issue

field should be fields

Current content

?field=metadata.enterprise_12345.contractTemplate

Expected content

?fields=metadata.enterprise_12345.contractTemplate

Link to the documentation page

https://developer.box.com/reference/get-folders-id-items/#param-fields

Small typo in Create Comment endpoint description

Hello,

Found a small typo in the description of the Create Comment endpoint, just thought I'd flag it. 😃

box-openapi/content/paths/comments__post_comments.yml

Line 12 in fcdfed8

Adds a comment comment by the user to a specific file, or

List group collaborations AND List pending collaborations - Collaboration response is missing order property

Description of the issue

It seems to be returning a collaborations resource in the response but the order property is missing from the collaborations resource.

Current content

array(4) { 'total_count' => int(0) 'entries' => array(0) { } 'offset' => int(0) 'limit' => int(100) }

Expected content

Collaborations properties should include:

entries
limit
offset
order (object)
total_count

List Folder Collaborations - response is not a collaborations resource

Description of the issue

This API response only contains a total_count and entries properties in the response.

Current content

array(2) { 'total_count' => int(0) 'entries' => array(0) { } }

Expected content

Collaborations properties should include:

entries
limit
offset
order (object)
total_count

Could not process model 'FileScope'

I tried to generate API client by OpenAPI Generator (https://github.com/OpenAPITools/openapi-generator). But it doesn't work.

takayama@takayama ~/work 
% LANG=C wget https://raw.githubusercontent.com/box/box-openapi/en/openapi.json
--2020-01-17 18:44:59--  https://raw.githubusercontent.com/box/box-openapi/en/openapi.json
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 151.101.228.133
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|151.101.228.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 824383 (805K) [text/plain]
Saving to: 'openapi.json'

openapi.json                  100%[=================================================>] 805.06K  2.22MB/s    in 0.4s    

2020-01-17 18:45:00 (2.22 MB/s) - 'openapi.json' saved [824383/824383]

takayama@takayama ~/work 
% openapi-generator generate -i ./openapi.json -g php -o ~/work/box-client     
[main] WARN  o.o.c.ignore.CodegenIgnoreProcessor - Output directory does not exist, or is inaccessible. No file (.openapi-generator-ignore) will be evaluated.
[main] INFO  o.o.codegen.DefaultGenerator - OpenAPI Generator: php (client)
[main] INFO  o.o.codegen.DefaultGenerator - Generator 'php' is considered stable.
[main] WARN  o.o.codegen.utils.ModelUtils - Multiple schemas found in content, returning only the first one
[main] WARN  o.o.codegen.utils.ModelUtils - Multiple schemas found in content, returning only the first one
[main] INFO  o.o.c.languages.AbstractPhpCodegen - Environment variable PHP_POST_PROCESS_FILE not defined so the PHP code may not be properly formatted. To define it, try 'export PHP_POST_PROCESS_FILE="/usr/local/bin/prettier --write"' (Linux/Mac)
[main] INFO  o.o.c.languages.AbstractPhpCodegen - NOTE: To enable file post-processing, 'enablePostProcessFile' must be set to `true` (--enable-post-process-file for CLI).
[main] WARN  o.o.codegen.DefaultCodegen - Unknown type found in the schema: object
[main] WARN  o.o.codegen.DefaultCodegen - Unknown type found in the schema: object
[main] WARN  o.o.codegen.DefaultCodegen - Unknown type found in the schema: object
[main] WARN  o.o.codegen.DefaultCodegen - Unknown type found in the schema: object
[main] WARN  o.o.codegen.DefaultCodegen - Unknown type found in the schema: object
[main] WARN  o.o.codegen.DefaultCodegen - Unknown type found in the schema: object
[main] WARN  o.o.codegen.DefaultCodegen - Unknown type found in the schema: object
[main] WARN  o.o.codegen.DefaultCodegen - Unknown type found in the schema: object
[main] WARN  o.o.codegen.utils.ModelUtils - [deprecated] inheritance without use of 'discriminator.propertyName' is deprecated and will be removed in a future release. Generating model for null
[main] WARN  o.o.codegen.DefaultCodegen - More than one inline schema specified in allOf:. Only the first one is recognized. All others are ignored.
[main] WARN  o.o.codegen.utils.ModelUtils - [deprecated] inheritance without use of 'discriminator.propertyName' is deprecated and will be removed in a future release. Generating model for null
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Item. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Item. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Item. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Item. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Item. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Item. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Item. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Item. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.utils.ModelUtils - [deprecated] inheritance without use of 'discriminator.propertyName' is deprecated and will be removed in a future release. Generating model for null
[main] WARN  o.o.codegen.utils.ModelUtils - [deprecated] inheritance without use of 'discriminator.propertyName' is deprecated and will be removed in a future release. Generating model for null
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Enterprise. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Enterprise. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Enterprise. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Enterprise. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Enterprise. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Enterprise. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Enterprise. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Enterprise. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.utils.ModelUtils - [deprecated] inheritance without use of 'discriminator.propertyName' is deprecated and will be removed in a future release. Generating model for null
[main] WARN  o.o.codegen.utils.ModelUtils - [deprecated] inheritance without use of 'discriminator.propertyName' is deprecated and will be removed in a future release. Generating model for null
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Enterprise. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Enterprise. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Enterprise. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Enterprise. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Enterprise. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Enterprise. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Enterprise. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Enterprise. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Enterprise. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Enterprise. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Enterprise. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Enterprise. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Enterprise. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Enterprise. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Enterprise. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Enterprise. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.utils.ModelUtils - [deprecated] inheritance without use of 'discriminator.propertyName' is deprecated and will be removed in a future release. Generating model for null
[main] WARN  o.o.codegen.utils.ModelUtils - [deprecated] inheritance without use of 'discriminator.propertyName' is deprecated and will be removed in a future release. Generating model for null
[main] WARN  o.o.codegen.utils.ModelUtils - [deprecated] inheritance without use of 'discriminator.propertyName' is deprecated and will be removed in a future release. Generating model for null
[main] WARN  o.o.codegen.utils.ModelUtils - [deprecated] inheritance without use of 'discriminator.propertyName' is deprecated and will be removed in a future release. Generating model for null
[main] WARN  o.o.codegen.DefaultCodegen - More than one inline schema specified in allOf:. Only the first one is recognized. All others are ignored.
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Reference. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Reference. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Reference. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Reference. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.utils.ModelUtils - [deprecated] inheritance without use of 'discriminator.propertyName' is deprecated and will be removed in a future release. Generating model for null
[main] WARN  o.o.codegen.utils.ModelUtils - [deprecated] inheritance without use of 'discriminator.propertyName' is deprecated and will be removed in a future release. Generating model for null
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Reference. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Reference. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Reference. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Reference. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Reference. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Reference. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Reference. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Reference. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.utils.ModelUtils - [deprecated] inheritance without use of 'discriminator.propertyName' is deprecated and will be removed in a future release. Generating model for null
[main] WARN  o.o.codegen.utils.ModelUtils - [deprecated] inheritance without use of 'discriminator.propertyName' is deprecated and will be removed in a future release. Generating model for null
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.utils.ModelUtils - [deprecated] inheritance without use of 'discriminator.propertyName' is deprecated and will be removed in a future release. Generating model for null
[main] WARN  o.o.codegen.utils.ModelUtils - [deprecated] inheritance without use of 'discriminator.propertyName' is deprecated and will be removed in a future release. Generating model for null
[main] WARN  o.o.codegen.utils.ModelUtils - [deprecated] inheritance without use of 'discriminator.propertyName' is deprecated and will be removed in a future release. Generating model for null
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: string. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: string. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: string. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: string. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Folder--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Folder--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Folder--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Folder--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.utils.ModelUtils - [deprecated] inheritance without use of 'discriminator.propertyName' is deprecated and will be removed in a future release. Generating model for null
[main] WARN  o.o.codegen.DefaultCodegen - More than one inline schema specified in allOf:. Only the first one is recognized. All others are ignored.
[main] WARN  o.o.codegen.utils.ModelUtils - [deprecated] inheritance without use of 'discriminator.propertyName' is deprecated and will be removed in a future release. Generating model for null
[main] WARN  o.o.codegen.DefaultCodegen - More than one inline schema specified in allOf:. Only the first one is recognized. All others are ignored.
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: string. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: string. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: string. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: string. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: PathCollection. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: PathCollection. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: PathCollection. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: PathCollection. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: SharedLink. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: SharedLink. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: SharedLink. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: SharedLink. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Folder--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Folder--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Folder--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Folder--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.utils.ModelUtils - [deprecated] inheritance without use of 'discriminator.propertyName' is deprecated and will be removed in a future release. Generating model for null
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: PathCollection. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: PathCollection. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: PathCollection. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: PathCollection. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: SharedLink. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: SharedLink. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: SharedLink. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: SharedLink. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Folder--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Folder--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Folder--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Folder--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: string. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: string. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: string. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: string. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: PathCollection. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: PathCollection. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: PathCollection. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: PathCollection. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: SharedLink. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: SharedLink. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: SharedLink. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: SharedLink. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Folder--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Folder--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Folder--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Folder--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.utils.ModelUtils - [deprecated] inheritance without use of 'discriminator.propertyName' is deprecated and will be removed in a future release. Generating model for null
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: string. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: string. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: string. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: string. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: string. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: string. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: string. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: string. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: File--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: File--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: File--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
[main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: File--Mini. To fully utilize allOf, please use $ref instead of inline schema definition
Exception in thread "main" java.lang.RuntimeException: Could not process model 'FileScope'.Please make sure that your schema is correct!
	at org.openapitools.codegen.DefaultGenerator.generateModels(DefaultGenerator.java:472)
	at org.openapitools.codegen.DefaultGenerator.generate(DefaultGenerator.java:923)
	at org.openapitools.codegen.cmd.Generate.run(Generate.java:416)
	at org.openapitools.codegen.OpenAPIGenerator.main(OpenAPIGenerator.java:61)
Caused by: java.lang.NullPointerException
	at org.openapitools.codegen.DefaultCodegen.updateCodegenPropertyEnum(DefaultCodegen.java:4319)
	at org.openapitools.codegen.DefaultCodegen.postProcessModelsEnum(DefaultCodegen.java:384)
	at org.openapitools.codegen.languages.AbstractPhpCodegen.postProcessModels(AbstractPhpCodegen.java:664)
	at org.openapitools.codegen.DefaultGenerator.processModels(DefaultGenerator.java:1199)
	at org.openapitools.codegen.DefaultGenerator.generateModels(DefaultGenerator.java:467)
	... 3 more
takayama@takayama ~/work 
%

enum property contains null. Is it unexpected item?

      "FileScope": {
        "title": "File Scope",
        "x-box-resource-id": "file_scope",
        "description": "A relation between a file and the scopes for which the file can be accessed",
        "properties": {
          "scope": {
            "type": "string",
            "description": "The file scopes for the file access",
            "example": "item_download",
            "enum": [
              "annotation_edit",
              "annotation_view_all",
              "annotation_view_self",
              "base_explorer",
              "base_picker",
              "base_preview",
              "base_upload",
              "item_delete",
              "item_download",
              "item_preview",
              "item_rename",
              "item_share",
              null
            ]
          },

File length defined as int32

Description of the issue

File sizes are defined as int32 in multiple places. This is not enough for larger file sizes.

Current content

    "/files/content": {
      "options": {
        "operationId": "options_files_content",
        "summary": "Preflight check before upload",
        "tags": [
          "Files"
        ],
        "x-box-tag": "uploads",
        "description": "Performs a check to verify that a file will be accepted by Box\nbefore you upload the entire file.",
        "requestBody": {
          "content": {
            "application/json": {
              "schema": {
                "type": "object",
                "properties": {
                  "name": {
                    "type": "string",
                    "description": "The name for the file",
                    "example": "File.mp4"
                  },
                  "size": {
                    "type": "integer",
                    "format": "int32",
                    "description": "The size of the file in bytes",
                    "example": 1024
                  },

Expected content

Type should be int64.

An in-range update of @stoplight/json-ref-resolver is breaking the build 🚨

The dependency @stoplight/json-ref-resolver was updated from `2.4.1` to `2.5.0`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@stoplight/json-ref-resolver is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

❌ Travis CI - Branch: The build errored.

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Error at 'Create metadata instance on file'

Description of the issue

When creating a metadata instance on a file where one already exists, receive ClientError object with status property empty. code property also differs from documentation.

Current content

{"message":"Conflict on Metadata Instance.","code":"conflict","request_id":"rfaeuqhlr9guyedg"}

Expected content

{"type":"error","status":"409","message":"An instance of them metadata template already exists on the file.","code":"tuple_already_exists","request_id":"rfaeuqhlr9guyedg","help_url":"http://developers.box.com/docs/#errors"}

Link to the documentation page

https://developer.box.com/reference/post-files-id-metadata-id-id/

Add samples

I think it will be a good idea to add java or .net samples of how to use this repo. Imagine I am totally new, this will really help

Upload-openapi definition contains invalid 'required' property

https://github.com/box/box-openapi/blob/master/v2.0/upload.openapi-v2.json#L1194

"required": "true"

should be

"required": true

Happy to submit a PR if the process is simply to amend the file.

The Open API Specification files are outdated

The Open API Specification files that Box provides at the Github URL
https://github.com/box/box-openapi/tree/master/v2.0
are outdated.

The new Open API Specification files should be made available at Github in some other branch
so that it will be in sync with the Box API that Box exposes to public.

event_type missing content setting

box-openapi/content/paths/events__get_events.yml

Line 85 in 3bacbea

- name: event_type

Please consult https://swagger.io/docs/specification/describing-parameters/#schema-vs-content

Add linting to the process

Add JSON linter
Add a reliable OpenAPI v3.0 linter
Ensure usage of tags is linted properly
Ensure spellcheck is performed properly
Ensure tone of voice is approximately inline

Clarify license

LICENSE and README state Apache 2.0 but OpenAPI definitions say MIT (with a link to http://github.com/gruntjs/grunt/blob/master/LICENSE-MIT) - linking directly to grunt's LICENSE seems to be a (mis)feature of APIMatic's API tooling.

Upload parameters out of order

According to the API documentation,
https://developer.box.com/v2.0/reference#upload-a-file

The "attributes" (JSON) part must come before the file part of the multipart form data.

However, in the spec the attributes is defined first.

Error at 'Enterprise (Base)'

Description of the issue

Now that Enterprise and Enterprise Plus are available, is the attribute type in enterprise object still going to "enterprise" always or will it say if it is Enterprise Plus as well?

Current content

In Entperise object, the field type always has enterprise.

Expected content

It should be Enterprise or Enterprise Plus based on the plan the user is on

Link to the documentation page

https://developer.box.com/reference/resources/enterprise--base/

`notification_email` object field in User returns empty list when not set

Hello,

When I make requests to Get Current User and Get User and didn't have the a notification email set for that user, I got back a empty list, rather than {} or null:

{
  "type": "user",
  "id": "***********",
  "name": "Name",
  "login": "[email protected]",
  "created_at": "2020-06-18T10:25:18-07:00",
  "modified_at": "2020-06-24T16:38:41-07:00",
  "language": "en",
  "timezone": "America/Los_Angeles",
  "space_amount": 10737418240,
  "space_used": 40595,
  "max_upload_size": 2147483648,
  "status": "active",
  "job_title": "",
  "phone": "222222222",
  "address": "",
  "avatar_url": "https://app.box.com/api/avatar/large/***********",
  "notification_email": []
}

However when I set a notification email for that user, I got back an object as expected from the spec:

{
  "type": "user",
  "id": "***********",
  "name": "Name",
  "login": "[email protected]",
  "created_at": "2020-06-18T10:25:18-07:00",
  "modified_at": "2020-06-24T20:37:24-07:00",
  "language": "en",
  "timezone": "America/Los_Angeles",
  "space_amount": 10737418240,
  "space_used": 40595,
  "max_upload_size": 2147483648,
  "status": "active",
  "job_title": "",
  "phone": "222222222",
  "address": "",
  "avatar_url": "https://app.box.com/api/avatar/large/***********",
  "notification_email": {
    "email": "[email protected]",
    "is_confirmed": true
  }
}

Just thought I'd flag this, and was wondering what usually happens in cases like these? Does the specification get updated or does the API itself get updated since they're different types depending on the case?

box-openapi/content/responses/user.yml

Lines 134 to 136 in fcdfed8

  notification_email: 

 x-box-field-variant: 2 

 type: object

file_extensions is a string not an array of strings

box-openapi/content/paths/search__get_search.yml

Line 82 in 900dacf

- name: file_extensions

Reformat Metadata Query results to return files/folders with metadata as field on items

The Box Metadata team is changing the response to the query api. We're combining metadata and the associated item and switching the item from Standard to Mini. Design (must be Box account): https://docs.google.com/document/d/1aIvZeOiTJggjuV3V1m_kUp-oUd5ZNhjLkjU51X7Gvog/edit?usp=sharing

Type of source_files in sign_request_create_request.yml should be an array of FileBase not FileMini

FileMini has sequence_id and sha1 required whereas the documentation for source_files states that only the members of FileBase are needed (id and type)

box-openapi/content/requests/sign_request_create_request.yml

Line 18 in 53ee1ff

$ref: '#/components/schemas/File--Mini'

Missing Offset and Marker query param in certain operations

Offset and Marker query params

I found out that 4 endpoints does not have query params.

files/:file_id/collaborations/
In the response we get offset parameter but we cannot set query param offset in order to paginate ?list_collaborations__get_files_id_collaborations.yml
DOCS: get-files-id-collaborations
folders/:folder_id/collaborations
In the response we get offset and limit parameters but we cannot set query params offset and limit in order to paginate ?
list_collaborations__get_folders_id_collaborations.yml
DOCS: get-folders-id-collaborations
folder_locks
In the response we get next_marker but we cannot set query param marker in order to paginate ?
folder_locks__get_folder_locks.yml
DOCS: get-folder-locks
metadata_templates
In the response we get next_marker but we cannot set query param marker in order to paginate ?
metadata_templates__get_metadata_templates.yml
DOCS: get-metadata-templates

Current content

Specification does not take into account those query params for operations.

Expected content

I tested all endpoints with the listed query params and no issue was found. Therefore, endpoints with the mentioned parameters should be included in the docs and specification.

Missing `type` field for associative array in Update Metadata Template

Hello,

It seems like the type field is missing from the associative array data in following:

box-openapi/content/attributes/metadata_template_operation.yml

Line 36 in 46deb09

data:

An in-range update of style-loader is breaking the build 🚨

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

The dependency style-loader was updated from `1.1.3` to `1.1.4`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

style-loader is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

❌ Travis CI - Branch: The build errored.

Release Notes for v1.1.4

1.1.4 (2020-04-15)

Chore

update deps

Commits

The new version differs by 3 commits.

171a747 chore(release): 1.1.4
af1b4a9 chore(deps): update
a003f05 docs: add links for the options table (#460)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Group resource into separate spec files

An in-range update of webpack is breaking the build 🚨

The dependency webpack was updated from `4.35.3` to `4.36.0`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

webpack is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

❌ Travis CI - Branch: The build errored.

Release Notes for v4.36.0

Features

SourceMapDevToolPlugin append option now supports the default placeholders in addition to [url]
Arrays in resolve and parser options (Rule and Loader API) support backreferences with "..." when overriding options.

Commits

The new version differs by 42 commits.

95d21bb 4.36.0
aa1216c Merge pull request #9422 from webpack/feature/dot-dot-dot-merge
b3ec775 improve merging of resolve and parsing options
53a5ae2 Merge pull request #9419 from vankop/remove-valid-jsdoc-rule
ab75240 Merge pull request #9413 from webpack/dependabot/npm_and_yarn/ajv-6.10.2
0bdabf4 Merge pull request #9418 from webpack/dependabot/npm_and_yarn/eslint-plugin-jsdoc-15.5.2
f207cdc remove valid jsdoc rule in favour of eslint-plugin-jsdoc
31333a6 chore(deps-dev): bump eslint-plugin-jsdoc from 15.3.9 to 15.5.2
036adf0 Merge pull request #9417 from webpack/dependabot/npm_and_yarn/eslint-plugin-jest-22.8.0
37d4480 Merge pull request #9411 from webpack/dependabot/npm_and_yarn/simple-git-1.121.0
ce2a183 chore(deps-dev): bump eslint-plugin-jest from 22.7.2 to 22.8.0
0beeb7e Merge pull request #9391 from vankop/create-hash-typescript
bf1a24a #9391 resolve super call discussion
bd7d95b #9391 resolve discussions, AbstractMethodError
4190638 chore(deps): bump ajv from 6.10.1 to 6.10.2

There are 42 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Typo fix and proposed re-wording

box-openapi/content/responses/metadata_template.yml

Line 109 in 9862aed

Whether or not to copy the metadata for a file or folder when an it is

Change to:
Whether or not to include the metadata when a file or folder is copied.

Missing `context_info` field in `Client Error`?

Hello,

I was making a request to the Create Folder endpoint with different payloads, some with missing required params to see how the response would look like, I get the following:

{
  "type": "error",
  "status": 400,
  "code": "bad_request",
  "context_info": {
    "errors": [
      {
        "reason": "missing_parameter",
        "name": "parent",
        "message": "'parent' is required"
      },
      {
        "reason": "missing_parameter",
        "name": "name",
        "message": "'name' is required"
      }
    ]
  },
  "help_url": "http://developers.box.com/docs/#errors",
  "message": "Bad Request",
  "request_id": "cksn44gg20atvj21"
}

I noticed the context_info field in the response however I couldn't find it in the spec for ClientError, was that intended or is it just missing from the spec?

box-openapi/content/errors/client_error.yml

Lines 11 to 69 in 3b6cb61

 properties: 

 type: 

 description: "`error`" 

 example: "error" 

 type: string 

 enum: 

 - error 

 nullable: false 

 status: 

 description: The HTTP status of the response. 

 example: 400 

 type: integer 

 format: int32 

 nullable: false 

 code: 

 description: A Box-specific error code 

 example: item_name_invalid 

 type: string 

 enum: 

 - created 

 - accepted 

 - no_content 

 - redirect 

 - not_modified 

 - bad_request 

 - unauthorized 

 - forbidden 

 - not_found 

 - method_not_allowed 

 - conflict 

 - precondition_failed 

 - too_many_requests 

 - internal_server_error 

 - unavailable 

 - item_name_invalid 

 help_url: 

 description: |- 

  A URL that links to more information about why this error occurred. 

  example: http://developers.box.com/docs/#errors 

 type: string 

 nullable: false 

 message: 

 description: |- 

  A short message describing the error. 

  example: Method Not Allowed 

 type: string 

 nullable: false 

 request_id: 

 description: |- 

  A unique identifier for this response, which can be used 

  when contacting Box support. 

  type: string 

 example: 'abcdef123456' 

 nullable: false

fields (comma seperated list) is a string not an array of string

The following attributes have wrongly defined schema:

box-openapi/content/attributes/fields.yml

Line 17 in fddf025

schema:

box-openapi/content/attributes/fields--with_metadata.yml

Line 22 in fddf025

schema:

List file collaborations - Does not return a collaborations resource in response

Description of the issue

See #149 for some context.

List file collaborations - 200 response is supposed to be a collaborations resource. But it seems this is incorrect.

It is returning this instead:
array(3) { 'next_marker' => string(0) "" 'previous_marker' => string(0) "" 'entries' => array(0) { } }

Current content

Expected content

It should probably be its own resource but I am unsure of how the Box team would want to handle this. Adding a new resource for a single endpoint seems not wise.

Error at 'Find folder for shared link'

Error at 'Get metadata instance on file'

Description of the issue

OK Response Code should be 200, not 201

Current content

201

Expected content

200

Link to the documentation page

https://developer.box.com/reference/get-files-id-metadata-id-id/

Migrate spec files to Open API v3

Migrate to v3
Ensure specs pass

Error at 'Add domain to list of allowed collaboration domains'

Description of the issue

the reponse code to adding a new domain successfully is 201 not 200.

Current content

200

Expected content

201

Link to the documentation page

https://developer.box.com/reference/post-collaboration-whitelist-entries/

Data type field missing for some parameters

Description of the issue

I am ingesting the openapi file in to my strictly typed project and noticed box openapi does not include the data type for each parameter.

Current content

no data types

Expected content

please add data types for each parameter

$ref where there shouldn't be a $ref

Description of the issue

Hey folks, I'm working with the OAI, looking for great projects using OpenAPI, and when I was checking out yours I noticed some invalid stuff going on. There are only a few specific places that a $ref is allowed, but unfortunately you've got them in places that are not valid.

This is just the output of popping https://raw.githubusercontent.com/box/box-openapi/main/content/openapi.yml into editor.swagger.io if you'd like to recreate it.

Swagger Editor isn't alone in struggling here, Stoplight Elements also will not load. https://elements-demo.stoplight.io/?spec=https://raw.githubusercontent.com/box/box-openapi/main/content/openapi.yml

I took a swing at fixing it by moving the contents of paths.yml and schemas.yml into the main openapi.yml, which helped a bit, but now I'm noticing more things which are technically not valid.

For example, inside content/paths/authorization__post_oauth2_token--refresh.yml I'm seeing $ref's pointing to #/components, but there is no components inside that file. I think it's trying to get back up to the main components in the openapi.yml which is not valid. Basically the # means "this file", so you'd need to $ref to "../openapi.yml#/components/schemas/foo" for that.

Exposing this much into the file system makes it feel brittle I know, but thankfully OpenAPI 3.1 has moved on to supporting $id's for bundling, which is a whole lot nicer. https://apisyouwonthate.com/blog/openapi-v3-1-and-json-schema

Anyhow, I bring this all up because doing invalid things will restrict your ability to use the widest variety of tooling, and leave you stuck on tools which happen to support your way of doing things. I know some do, but might be better to get to being valid OpenAPI all the same.

Or, if you think OpenAPI should change to support the way you use $ref, perhaps you could join one of the https://lists.openapis.org/g/tsc/calendar calls to raise the topic? We love participation and it makes the spec better for everyone!

Inconsistent response content schema in `post_legal_hold_policies`

Hello, I found the following in the OpenAPI spec for the response code 400 of the post_legal_hold_policies path:

"400": {
  "description": "Returns an error if required parameters are missing,\nor neither `is_ongoing` or filter dates are specified.",
  "content": {
    "application/json": {
      "schema": {
        "$ref": "#/components/schemas/LegalHoldPolicy"
      }
    }
  }
}

It seems like it should be "$ref": "#/components/schemas/ClientError" instead in

box-openapi/content/paths/legal_hold_policies__post_legal_hold_policies.yml

Line 101 in fe20b0e

$ref: '#/components/schemas/LegalHoldPolicy'

Collaborations - Response contains wrong properties?

Description of the issue

The properties or the response of the Collaborations resource seem wrong.

I am expecting to see:

What I am actually seeing is:

array(3) { 'next_marker' => string(0) "" 'previous_marker' => string(0) "" 'entries' => array(0) { } }

I will submit a pull request for what I am seeing but it seems odd that the documentation is so far off on this.

Current content

Currently the response is:

entries
next_marker
prev_marker

Expected content

What is listed in the api reference

Updating collaborations shows as POST in Splunk and returns 204

Description

When updating a collaboration via Postman or cURL, even when not changing owners, a 204 response code is returned. Potentially as a result, all of these requests are showing up in Splunk as POST requests instead of PUT.

Next steps

Internal investigation needed to see if this is intended behavior. Opening this ticket to document the current behavior in case we need to amend docs

Error at 'Create folder'

Description of the issue

The requirements on the 'name' request field should indicate that the name will be compared case-insensitively to existing names, and any names found to be the same will trigger a 409 error with message 'Item with the same name already exists'. For example, folder "Payments" cannot be created if there is already a "payments" in the same folder.

Current content

Nothing about this, nor any option to request a case-sensitive comparison instead.

Expected content

Would describe this default behavior, and provide a field to override.

Link to the documentation page

https://developer.box.com/reference/post-folders/

Wrong base url in "upload file" endpoint

Description of the issue

Incorrect base url mapped for CURL example For Upload File and all upload endpoints where base url should be "https://upload.box.com" instead of "https://api.box.com"

Current content

curl -i -X POST "**https://api.box.com/**2.0/files/content"
-H "authorization: Bearer <ACCESS_TOKEN>"
-H "content-type: multipart/form-data"
-F attributes='{"name":"Contract.pdf", "parent":{"id":"11446498"}}'
-F file=@<FILE_NAME>

Expected content

curl -i -X POST "**https://upload.box.com/api/**2.0/files/content"
-H "authorization: Bearer <ACCESS_TOKEN>"
-H "content-type: multipart/form-data"
-F attributes='{"name":"Contract.pdf", "parent":{"id":"11446498"}}'
-F file=@<FILE_NAME>

Link to the documentation page

https://developer.box.com/reference/post-files-content/

Documentation of various types inconsistent with example responses

Description of the issue

Currently the documentation for File (base) says id has type string, but the example json shows numeric:

{
  "id": 12345,
  "type": "file",
  "etag": 1,
}

The actual openapi definition also says string. The same stands for etag and other fields throughout the documentation on various types (but have not done a thorough inspection of all the examples).

I am not a Boxer (assuming that means employee of Box).

I would provide a PR if i knew which direction the fix should go in. I imagine its the example that is wrong because the API currently responds with numeric values, but cannot be certain.

Current content

{
  "id": 12345,
  "type": "file",
  "etag": 1,
}

Expected content

{
  "id": "12345",
  "type": "file",
  "etag": "1",
}

Recommend Projects

React

A declarative, efficient, and flexible JavaScript library for building user interfaces.
Vue.js

🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript

TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
TensorFlow

An Open Source Machine Learning Framework for Everyone
Django

The Web framework for perfectionists with deadlines.
Laravel

A PHP framework for web artisans
D3

Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

javascript

JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
web

Some thing interesting about web. New door for the world.
server

A server is a program made to process requests and deliver data to clients.
Machine learning

Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Visualization

Some thing interesting about visualization, use data art
Game

Some thing interesting about game, make everyone happy.

Recommend Org

Facebook

We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft

Open source projects and samples from Microsoft.
Google

Google ❤️ Open Source for everyone.
Alibaba

Alibaba Open Source for everyone
D3

Data-Driven Documents codes.
Tencent

China tencent open source team.

	properties:
	type:
	description: "`error`"
	example: "error"
	type: string
	enum:
	- error
	nullable: false

	status:
	description: The HTTP status of the response.
	example: 400
	type: integer
	format: int32
	nullable: false

	code:
	description: A Box-specific error code
	example: item_name_invalid
	type: string
	enum:
	- created
	- accepted
	- no_content
	- redirect
	- not_modified
	- bad_request
	- unauthorized
	- forbidden
	- not_found
	- method_not_allowed
	- conflict
	- precondition_failed
	- too_many_requests
	- internal_server_error
	- unavailable
	- item_name_invalid

	help_url:
	description: \|-
	A URL that links to more information about why this error occurred.
	example: http://developers.box.com/docs/#errors
	type: string
	nullable: false

	message:
	description: \|-
	A short message describing the error.
	example: Method Not Allowed
	type: string
	nullable: false

	request_id:
	description: \|-
	A unique identifier for this response, which can be used
	when contacting Box support.
	type: string
	example: 'abcdef123456'
	nullable: false

box / box-openapi Goto Github PK

box-openapi's People

Stargazers

Watchers

Forkers

box-openapi's Issues

Description of the issue

Current content

Expected content

Description of the issue

Current content

Expected content

Description of the issue

Current content

Expected content

Description of the issue

Current content

Expected content

Link to the documentation page

Description of the issue

Current content

Expected content

Description of the issue

Current content

Expected content

Description of the issue

Current content

Expected content

The dependency @stoplight/json-ref-resolver was updated from 2.4.1 to 2.5.0.

Description of the issue

Current content

Expected content

Link to the documentation page

Description of the issue

Current content

Expected content

Link to the documentation page

Offset and Marker query params

Current content

Expected content

The dependency style-loader was updated from 1.1.3 to 1.1.4.

1.1.4 (2020-04-15)

Chore

The dependency webpack was updated from 4.35.3 to 4.36.0.

Features

Description of the issue

Current content

Expected content

Description of the issue

Current content

Expected content

Link to the documentation page

Description of the issue

Current content

Expected content

Link to the documentation page

Description of the issue

Current content

Expected content

Description of the issue

Description of the issue

Current content

Expected content

Description

Next steps

Description of the issue

Current content

Expected content

Link to the documentation page

Description of the issue

Current content

Expected content

Link to the documentation page

Description of the issue

Current content

Expected content

Recommend Projects

Recommend Topics

Recommend Org

The dependency @stoplight/json-ref-resolver was updated from `2.4.1` to `2.5.0`.

The dependency style-loader was updated from `1.1.3` to `1.1.4`.

The dependency webpack was updated from `4.35.3` to `4.36.0`.