@openfilz-sdk/typescript 1.3.36 → 1.3.37

package/.openapi-generator/openfilz-api-generate-typescript-sdk.sha256

@@ -1 +1 @@
-fd80ce671912b5791db2da2fe2b4559ac53317cfbd48ef51d48992c63ec23beb
+2f943b97f36fa000395c33ffd1c195df26a8f385b1aabc03dba438e24da830a7

package/README.md

@@ -1,4 +1,4 @@
-## @openfilz-sdk/typescript@1.3.36
+## @openfilz-sdk/typescript@1.3.37
 
 This generator creates TypeScript/JavaScript client that utilizes [axios](https://github.com/axios/axios). The generated Node module can be used in the following environments:
 
@@ -36,7 +36,7 @@ navigate to the folder of your consuming project and run one of the following co
 _published:_
 
 ```
-npm install @openfilz-sdk/typescript@1.3.36 --save
+npm install @openfilz-sdk/typescript@1.3.37 --save
 ```
 
 _unPublished (not recommended):_

package/api/aichat-api.ts

@@ -306,7 +306,7 @@ export const AIChatApiAxiosParamCreator = function (configuration?: Configuratio
             };
         },
         /**
-         * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…), and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
+         * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…) or else in the request\'s language, and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
          * @summary Propose a reorganisation by kind of document — no model involved
          * @param {ReorganizationByKindRequest} [reorganizationByKindRequest] 
          * @param {*} [options] Override http request option.
@@ -443,7 +443,7 @@ export const AIChatApiFp = function(configuration?: Configuration) {
             return (axios, basePath) => createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration)(axios, localVarOperationServerBasePath || basePath);
         },
         /**
-         * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…), and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
+         * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…) or else in the request\'s language, and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
          * @summary Propose a reorganisation by kind of document — no model involved
          * @param {ReorganizationByKindRequest} [reorganizationByKindRequest] 
          * @param {*} [options] Override http request option.
@@ -535,7 +535,7 @@ export const AIChatApiFactory = function (configuration?: Configuration, basePat
             return localVarFp.listConversations(options).then((request) => request(axios, basePath));
         },
         /**
-         * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…), and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
+         * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…) or else in the request\'s language, and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
          * @summary Propose a reorganisation by kind of document — no model involved
          * @param {ReorganizationByKindRequest} [reorganizationByKindRequest] 
          * @param {*} [options] Override http request option.
@@ -629,7 +629,7 @@ export class AIChatApi extends BaseAPI {
     }
 
     /**
-     * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…), and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
+     * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…) or else in the request\'s language, and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
      * @summary Propose a reorganisation by kind of document — no model involved
      * @param {ReorganizationByKindRequest} [reorganizationByKindRequest] 
      * @param {*} [options] Override http request option.

package/dist/api/aichat-api.d.ts

@@ -80,7 +80,7 @@ export declare const AIChatApiAxiosParamCreator: (configuration?: Configuration)
      */
     listConversations: (options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
     /**
-     * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…), and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
+     * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…) or else in the request\'s language, and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
      * @summary Propose a reorganisation by kind of document — no model involved
      * @param {ReorganizationByKindRequest} [reorganizationByKindRequest]
      * @param {*} [options] Override http request option.
@@ -149,7 +149,7 @@ export declare const AIChatApiFp: (configuration?: Configuration) => {
      */
     listConversations(options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<Array<AiChatConversation>>>;
     /**
-     * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…), and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
+     * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…) or else in the request\'s language, and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
      * @summary Propose a reorganisation by kind of document — no model involved
      * @param {ReorganizationByKindRequest} [reorganizationByKindRequest]
      * @param {*} [options] Override http request option.
@@ -218,7 +218,7 @@ export declare const AIChatApiFactory: (configuration?: Configuration, basePath?
      */
     listConversations(options?: RawAxiosRequestConfig): AxiosPromise<Array<AiChatConversation>>;
     /**
-     * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…), and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
+     * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…) or else in the request\'s language, and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
      * @summary Propose a reorganisation by kind of document — no model involved
      * @param {ReorganizationByKindRequest} [reorganizationByKindRequest]
      * @param {*} [options] Override http request option.
@@ -287,7 +287,7 @@ export declare class AIChatApi extends BaseAPI {
      */
     listConversations(options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<AiChatConversation[], any, {}>>;
     /**
-     * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…), and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
+     * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…) or else in the request\'s language, and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
      * @summary Propose a reorganisation by kind of document — no model involved
      * @param {ReorganizationByKindRequest} [reorganizationByKindRequest]
      * @param {*} [options] Override http request option.

package/dist/api/aichat-api.js

@@ -265,7 +265,7 @@ const AIChatApiAxiosParamCreator = function (configuration) {
             };
         }),
         /**
-         * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…), and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
+         * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…) or else in the request\'s language, and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
          * @summary Propose a reorganisation by kind of document — no model involved
          * @param {ReorganizationByKindRequest} [reorganizationByKindRequest]
          * @param {*} [options] Override http request option.
@@ -418,7 +418,7 @@ const AIChatApiFp = function (configuration) {
             });
         },
         /**
-         * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…), and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
+         * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…) or else in the request\'s language, and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
          * @summary Propose a reorganisation by kind of document — no model involved
          * @param {ReorganizationByKindRequest} [reorganizationByKindRequest]
          * @param {*} [options] Override http request option.
@@ -513,7 +513,7 @@ const AIChatApiFactory = function (configuration, basePath, axios) {
             return localVarFp.listConversations(options).then((request) => request(axios, basePath));
         },
         /**
-         * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…), and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
+         * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…) or else in the request\'s language, and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
          * @summary Propose a reorganisation by kind of document — no model involved
          * @param {ReorganizationByKindRequest} [reorganizationByKindRequest]
          * @param {*} [options] Override http request option.
@@ -600,7 +600,7 @@ class AIChatApi extends base_1.BaseAPI {
         return (0, exports.AIChatApiFp)(this.configuration).listConversations(options).then((request) => request(this.axios, this.basePath));
     }
     /**
-     * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…), and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
+     * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…) or else in the request\'s language, and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
      * @summary Propose a reorganisation by kind of document — no model involved
      * @param {ReorganizationByKindRequest} [reorganizationByKindRequest]
      * @param {*} [options] Override http request option.

package/dist/esm/api/aichat-api.d.ts

@@ -80,7 +80,7 @@ export declare const AIChatApiAxiosParamCreator: (configuration?: Configuration)
      */
     listConversations: (options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
     /**
-     * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…), and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
+     * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…) or else in the request\'s language, and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
      * @summary Propose a reorganisation by kind of document — no model involved
      * @param {ReorganizationByKindRequest} [reorganizationByKindRequest]
      * @param {*} [options] Override http request option.
@@ -149,7 +149,7 @@ export declare const AIChatApiFp: (configuration?: Configuration) => {
      */
     listConversations(options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<Array<AiChatConversation>>>;
     /**
-     * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…), and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
+     * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…) or else in the request\'s language, and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
      * @summary Propose a reorganisation by kind of document — no model involved
      * @param {ReorganizationByKindRequest} [reorganizationByKindRequest]
      * @param {*} [options] Override http request option.
@@ -218,7 +218,7 @@ export declare const AIChatApiFactory: (configuration?: Configuration, basePath?
      */
     listConversations(options?: RawAxiosRequestConfig): AxiosPromise<Array<AiChatConversation>>;
     /**
-     * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…), and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
+     * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…) or else in the request\'s language, and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
      * @summary Propose a reorganisation by kind of document — no model involved
      * @param {ReorganizationByKindRequest} [reorganizationByKindRequest]
      * @param {*} [options] Override http request option.
@@ -287,7 +287,7 @@ export declare class AIChatApi extends BaseAPI {
      */
     listConversations(options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<AiChatConversation[], any, {}>>;
     /**
-     * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…), and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
+     * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…) or else in the request\'s language, and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
      * @summary Propose a reorganisation by kind of document — no model involved
      * @param {ReorganizationByKindRequest} [reorganizationByKindRequest]
      * @param {*} [options] Override http request option.

package/dist/esm/api/aichat-api.js

@@ -262,7 +262,7 @@ export const AIChatApiAxiosParamCreator = function (configuration) {
             };
         }),
         /**
-         * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…), and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
+         * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…) or else in the request\'s language, and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
          * @summary Propose a reorganisation by kind of document — no model involved
          * @param {ReorganizationByKindRequest} [reorganizationByKindRequest]
          * @param {*} [options] Override http request option.
@@ -414,7 +414,7 @@ export const AIChatApiFp = function (configuration) {
             });
         },
         /**
-         * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…), and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
+         * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…) or else in the request\'s language, and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
          * @summary Propose a reorganisation by kind of document — no model involved
          * @param {ReorganizationByKindRequest} [reorganizationByKindRequest]
          * @param {*} [options] Override http request option.
@@ -508,7 +508,7 @@ export const AIChatApiFactory = function (configuration, basePath, axios) {
             return localVarFp.listConversations(options).then((request) => request(axios, basePath));
         },
         /**
-         * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…), and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
+         * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…) or else in the request\'s language, and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
          * @summary Propose a reorganisation by kind of document — no model involved
          * @param {ReorganizationByKindRequest} [reorganizationByKindRequest]
          * @param {*} [options] Override http request option.
@@ -594,7 +594,7 @@ export class AIChatApi extends BaseAPI {
         return AIChatApiFp(this.configuration).listConversations(options).then((request) => request(this.axios, this.basePath));
     }
     /**
-     * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…), and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
+     * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…) or else in the request\'s language, and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
      * @summary Propose a reorganisation by kind of document — no model involved
      * @param {ReorganizationByKindRequest} [reorganizationByKindRequest]
      * @param {*} [options] Override http request option.

package/dist/esm/models/reorganization-by-kind-request.d.ts

@@ -11,4 +11,5 @@
  */
 export interface ReorganizationByKindRequest {
     'rootFolderId'?: string;
+    'language'?: string;
 }

package/dist/models/reorganization-by-kind-request.d.ts

@@ -11,4 +11,5 @@
  */
 export interface ReorganizationByKindRequest {
     'rootFolderId'?: string;
+    'language'?: string;
 }

package/docs/AIChatApi.md

@@ -370,7 +370,7 @@ This endpoint does not have any parameters.
 # **proposeByKind**
 > ReorganizationPlanView proposeByKind()
 
-Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…), and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
+Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…) or else in the request\'s language, and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
 
 ### Example
 

package/docs/ReorganizationByKindRequest.md

@@ -6,6 +6,7 @@
 Name | Type | Description | Notes
 ------------ | ------------- | ------------- | -------------
 **rootFolderId** | **string** |  | [optional] [default to undefined]
+**language** | **string** |  | [optional] [default to undefined]
 
 ## Example
 
@@ -14,6 +15,7 @@ import { ReorganizationByKindRequest } from '@openfilz-sdk/typescript';
 
 const instance: ReorganizationByKindRequest = {
     rootFolderId,
+    language,
 };
 ```
 

package/docs/TusControllerApi.md

@@ -374,6 +374,7 @@ void (empty response body)
 |-------------|-------------|------------------|
 |**200** | Upload info returned |  * Tus-Resumable - TUS protocol version <br>  * Upload-Offset - New offset after this chunk <br>  * Upload-Length - Total file size in bytes <br>  |
 |**404** | Upload not found |  -  |
+|**410** | Upload expired before it was complete - start it again |  -  |
 
 [[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md)
 
@@ -487,6 +488,7 @@ const { status, data } = await apiInstance.uploadChunk(
 |-------------|-------------|------------------|
 |**204** | Chunk received successfully |  * Tus-Resumable - TUS protocol version <br>  * Upload-Offset - New offset after this chunk <br>  |
 |**409** | Offset mismatch - resume from HEAD request |  -  |
+|**410** | Upload expired - start it again |  -  |
 |**413** | The chunk would go past the declared Upload-Length |  -  |
 |**404** | Upload not found |  -  |
 

package/models/reorganization-by-kind-request.ts

@@ -16,5 +16,6 @@
 
 export interface ReorganizationByKindRequest {
     'rootFolderId'?: string;
+    'language'?: string;
 }
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@openfilz-sdk/typescript",
-  "version": "1.3.36",
+  "version": "1.3.37",
   "description": "OpenAPI client for @openfilz-sdk/typescript",
   "author": "OpenAPI-Generator Contributors",
   "repository": {