@dangl/avacloud-client-node 1.63.9-beta0001-avacloud-preview → 1.64.1-avacloud-preview

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (8) hide show
  1. package/LICENSE.md +14 -14
  2. package/README.md +21 -21
  3. package/api.d.ts +38 -13
  4. package/api.js +728 -1588
  5. package/api.js.map +1 -1
  6. package/api.ts +1055 -1734
  7. package/package.json +14 -14
  8. package/tsconfig.json +16 -16
package/LICENSE.md CHANGED
@@ -1,14 +1,14 @@
1
- ### Licence
2
-
3
- #### Copyright (c) 2025 Dangl IT GmbH, [https://www.dangl-it.com](https://www.dangl-it.com)
4
-
5
- This software shall only be used for non-commercial evaluation purposes.
6
- Please contact Dangl**IT** for a commercial licence.
7
-
8
- THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
9
- IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
10
- FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.IN NO EVENT SHALL THE
11
- AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
12
- LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
13
- OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
14
- THE SOFTWARE.
1
+ ### Licence
2
+
3
+ #### Copyright (c) 2026 Dangl IT GmbH, [https://www.dangl-it.com](https://www.dangl-it.com)
4
+
5
+ This software shall only be used for non-commercial evaluation purposes.
6
+ Please contact Dangl**IT** for a commercial licence.
7
+
8
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
9
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
10
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.IN NO EVENT SHALL THE
11
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
12
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
13
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
14
+ THE SOFTWARE.
package/README.md CHANGED
@@ -1,23 +1,23 @@
1
- # Dangl.AVACloud Client
2
-
3
- This code was automatically generated. It is based on the [AVACloud API Specification](https://avacloud-api.dangl-it.com/swagger).
4
- AVACloud is a web service for working with GAEB files - convert, repair, create and transform - on any platform.
5
- Please visit [https://www.dangl-it.com]([https://www.dangl-it.com) for more information and step-by-step tutorials for each client library.
6
-
7
- The generator is available at:
1
+ # Dangl.AVACloud Client
2
+
3
+ This code was automatically generated. It is based on the [AVACloud API Specification](https://avacloud-api.dangl-it.com/swagger).
4
+ AVACloud is a web service for working with GAEB files - convert, repair, create and transform - on any platform.
5
+ Please visit [https://www.dangl-it.com]([https://www.dangl-it.com) for more information and step-by-step tutorials for each client library.
6
+
7
+ The generator is available at:
8
8
  https://github.com/Dangl-IT/Dangl.AVACloudClientGenerator
9
9
 
10
- ## Update Notice
11
-
12
- Starting with version **1.30.0**, the package dropped external dependencies and did some refactoring to the code. The following changes are required:
13
-
14
- * `FileParameter` now uses `data` instead of `value` for the file content
15
- * `FileParameter` now uses `fileName` instead of `options.filename` for the file name
16
- * All responses are now wrapped in a response object, making it easier to access e.g. returned headers or status codes
17
- * File responses now return a `Blob` instead of an `Buffer`, and are accessible via `response.result` instead of `response.body`
18
-
19
-
20
-
21
-
22
- ---
23
- [License](./LICENSE.md)
10
+ ## Update Notice
11
+
12
+ Starting with version **1.30.0**, the package dropped external dependencies and did some refactoring to the code. The following changes are required:
13
+
14
+ * `FileParameter` now uses `data` instead of `value` for the file content
15
+ * `FileParameter` now uses `fileName` instead of `options.filename` for the file name
16
+ * All responses are now wrapped in a response object, making it easier to access e.g. returned headers or status codes
17
+ * File responses now return a `Blob` instead of an `Buffer`, and are accessible via `response.result` instead of `response.body`
18
+
19
+
20
+
21
+
22
+ ---
23
+ [License](./LICENSE.md)
package/api.d.ts CHANGED
@@ -1169,20 +1169,33 @@ export declare class OenormConversionApi {
1169
1169
  oenormConversionConvertToAvaWithRequestObject(oenormFile: FileParameter | null | undefined, options?: {
1170
1170
  removePlainTextLongTexts?: boolean | undefined;
1171
1171
  removeHtmlLongTexts?: boolean | undefined;
1172
+ useOenormFileDeclarationForItemNumberSchema?: boolean | undefined;
1172
1173
  }): Promise<SwaggerResponse<ProjectDto>>;
1173
1174
  /**
1174
1175
  * Converts ÖNorm files to Dangl.AVA projects
1175
1176
  * @param oenormFile (optional) The input file
1176
1177
  * @param removePlainTextLongTexts (optional) If set to true, plain text long texts will be removed from the output to reduce response sizes
1177
1178
  * @param removeHtmlLongTexts (optional) If set to true, html long texts will be removed from the output to reduce response sizes
1179
+ * @param useOenormFileDeclarationForItemNumberSchema (optional) If this is enabled, then the actual content structure inside the ÖNorm file is ignored. The item number
1180
+ schema of the target will be built based on the top level structure definition of the ÖNorm file, even if the
1181
+ file content itself might be different or empty
1178
1182
  */
1179
- oenormConversionConvertToAva(oenormFile: FileParameter | null | undefined, removePlainTextLongTexts?: boolean | undefined, removeHtmlLongTexts?: boolean | undefined): Promise<SwaggerResponse<ProjectDto>>;
1183
+ oenormConversionConvertToAva(oenormFile: FileParameter | null | undefined, removePlainTextLongTexts?: boolean | undefined, removeHtmlLongTexts?: boolean | undefined, useOenormFileDeclarationForItemNumberSchema?: boolean | undefined): Promise<SwaggerResponse<ProjectDto>>;
1180
1184
  protected processOenormConversionConvertToAva(response: Response): Promise<SwaggerResponse<ProjectDto>>;
1185
+ /**
1186
+ * This is a generated method that accepts an options object, it simply calls the generated method with the parameter list
1187
+ */
1188
+ oenormConversionConvertToFlatAvaWithRequestObject(oenormFile: FileParameter | null | undefined, options?: {
1189
+ useOenormFileDeclarationForItemNumberSchema?: boolean | undefined;
1190
+ }): Promise<SwaggerResponse<FlatAvaProject>>;
1181
1191
  /**
1182
1192
  * Converts ÖNorm files to Dangl.AVA projects
1183
1193
  * @param oenormFile (optional) The input file
1194
+ * @param useOenormFileDeclarationForItemNumberSchema (optional) If this is enabled, then the actual content structure inside the ÖNorm file is ignored. The item number
1195
+ schema of the target will be built based on the top level structure definition of the ÖNorm file, even if the
1196
+ file content itself might be different or empty
1184
1197
  */
1185
- oenormConversionConvertToFlatAva(oenormFile: FileParameter | null | undefined): Promise<SwaggerResponse<FlatAvaProject>>;
1198
+ oenormConversionConvertToFlatAva(oenormFile: FileParameter | null | undefined, useOenormFileDeclarationForItemNumberSchema?: boolean | undefined): Promise<SwaggerResponse<FlatAvaProject>>;
1186
1199
  protected processOenormConversionConvertToFlatAva(response: Response): Promise<SwaggerResponse<FlatAvaProject>>;
1187
1200
  /**
1188
1201
  * This is a generated method that accepts an options object, it simply calls the generated method with the parameter list
@@ -1195,6 +1208,7 @@ export declare class OenormConversionApi {
1195
1208
  removeUnprintableCharactersFromTexts?: boolean | undefined;
1196
1209
  forceIncludeDescriptions?: boolean | undefined;
1197
1210
  treatNullItemNumberSchemaAsInvalid?: boolean | undefined;
1211
+ useOenormFileDeclarationForItemNumberSchema?: boolean | undefined;
1198
1212
  }): Promise<SwaggerResponse<FileResponse>>;
1199
1213
  /**
1200
1214
  * Converts ÖNorm files to GAEB files.
@@ -1226,8 +1240,11 @@ export declare class OenormConversionApi {
1226
1240
  With this setting, you can also tell AVACloud to treat a null value as invalid. Otherwise, null schemas will simply be ignored
1227
1241
  and not lead to any schema being generated. It is recommended to enable this option, but it is disabled by default for compatibility
1228
1242
  reasons.
1243
+ * @param useOenormFileDeclarationForItemNumberSchema (optional) If this is enabled, then the actual content structure inside the ÖNorm file is ignored. The item number
1244
+ schema of the target will be built based on the top level structure definition of the ÖNorm file, even if the
1245
+ file content itself might be different or empty
1229
1246
  */
1230
- oenormConversionConvertToGaeb(oenormFile: FileParameter | null | undefined, destinationGaebType?: DestinationGaebType | undefined, targetExchangePhaseTransform?: DestinationGaebExchangePhase | undefined, enforceStrictOfferPhaseLongTextOutput?: boolean | undefined, exportQuantityDetermination?: boolean | undefined, removeUnprintableCharactersFromTexts?: boolean | undefined, forceIncludeDescriptions?: boolean | undefined, treatNullItemNumberSchemaAsInvalid?: boolean | undefined): Promise<SwaggerResponse<FileResponse>>;
1247
+ oenormConversionConvertToGaeb(oenormFile: FileParameter | null | undefined, destinationGaebType?: DestinationGaebType | undefined, targetExchangePhaseTransform?: DestinationGaebExchangePhase | undefined, enforceStrictOfferPhaseLongTextOutput?: boolean | undefined, exportQuantityDetermination?: boolean | undefined, removeUnprintableCharactersFromTexts?: boolean | undefined, forceIncludeDescriptions?: boolean | undefined, treatNullItemNumberSchemaAsInvalid?: boolean | undefined, useOenormFileDeclarationForItemNumberSchema?: boolean | undefined): Promise<SwaggerResponse<FileResponse>>;
1231
1248
  protected processOenormConversionConvertToGaeb(response: Response): Promise<SwaggerResponse<FileResponse>>;
1232
1249
  /**
1233
1250
  * This is a generated method that accepts an options object, it simply calls the generated method with the parameter list
@@ -1238,6 +1255,7 @@ export declare class OenormConversionApi {
1238
1255
  conversionCulture?: string | null | undefined;
1239
1256
  includeArticleNumbers?: boolean | undefined;
1240
1257
  lockAllCellsButPrices?: boolean | undefined;
1258
+ useOenormFileDeclarationForItemNumberSchema?: boolean | undefined;
1241
1259
  }): Promise<SwaggerResponse<FileResponse>>;
1242
1260
  /**
1243
1261
  * Converts ÖNorm files to Excel
@@ -1251,8 +1269,11 @@ export declare class OenormConversionApi {
1251
1269
  'position.commerceProperties.articleNumber'
1252
1270
  * @param lockAllCellsButPrices (optional) If this is enabled, then all cells except the unit price cells will
1253
1271
  be locked, so users can not accidentally modify other fields.
1272
+ * @param useOenormFileDeclarationForItemNumberSchema (optional) If this is enabled, then the actual content structure inside the ÖNorm file is ignored. The item number
1273
+ schema of the target will be built based on the top level structure definition of the ÖNorm file, even if the
1274
+ file content itself might be different or empty
1254
1275
  */
1255
- oenormConversionConvertToExcel(oenormFile: FileParameter | null | undefined, writePrices?: boolean | undefined, writeLongTexts?: boolean | undefined, conversionCulture?: string | null | undefined, includeArticleNumbers?: boolean | undefined, lockAllCellsButPrices?: boolean | undefined): Promise<SwaggerResponse<FileResponse>>;
1276
+ oenormConversionConvertToExcel(oenormFile: FileParameter | null | undefined, writePrices?: boolean | undefined, writeLongTexts?: boolean | undefined, conversionCulture?: string | null | undefined, includeArticleNumbers?: boolean | undefined, lockAllCellsButPrices?: boolean | undefined, useOenormFileDeclarationForItemNumberSchema?: boolean | undefined): Promise<SwaggerResponse<FileResponse>>;
1256
1277
  protected processOenormConversionConvertToExcel(response: Response): Promise<SwaggerResponse<FileResponse>>;
1257
1278
  /**
1258
1279
  * This is a generated method that accepts an options object, it simply calls the generated method with the parameter list
@@ -1262,6 +1283,7 @@ export declare class OenormConversionApi {
1262
1283
  tryRepairProjectStructure?: boolean | undefined;
1263
1284
  skipTryEnforceSchemaCompliantXmlOutput?: boolean | undefined;
1264
1285
  removeUnprintableCharactersFromTexts?: boolean | undefined;
1286
+ useOenormFileDeclarationForItemNumberSchema?: boolean | undefined;
1265
1287
  }): Promise<SwaggerResponse<FileResponse>>;
1266
1288
  /**
1267
1289
  * Converts ÖNorm files to Oenorm files.
@@ -1275,8 +1297,11 @@ export declare class OenormConversionApi {
1275
1297
  * @param removeUnprintableCharactersFromTexts (optional) If this is enabled, unprintable characters are removed from text elements. Otherwise, the conversion
1276
1298
  might fail in case some text content contains characters that are not allowed in XML output formats.
1277
1299
  Defaults to true.
1300
+ * @param useOenormFileDeclarationForItemNumberSchema (optional) If this is enabled, then the actual content structure inside the ÖNorm file is ignored. The item number
1301
+ schema of the target will be built based on the top level structure definition of the ÖNorm file, even if the
1302
+ file content itself might be different or empty
1278
1303
  */
1279
- oenormConversionConvertToOenorm(oenormFile: FileParameter | null | undefined, destinationOenormType?: DestinationOenormType | undefined, tryRepairProjectStructure?: boolean | undefined, skipTryEnforceSchemaCompliantXmlOutput?: boolean | undefined, removeUnprintableCharactersFromTexts?: boolean | undefined): Promise<SwaggerResponse<FileResponse>>;
1304
+ oenormConversionConvertToOenorm(oenormFile: FileParameter | null | undefined, destinationOenormType?: DestinationOenormType | undefined, tryRepairProjectStructure?: boolean | undefined, skipTryEnforceSchemaCompliantXmlOutput?: boolean | undefined, removeUnprintableCharactersFromTexts?: boolean | undefined, useOenormFileDeclarationForItemNumberSchema?: boolean | undefined): Promise<SwaggerResponse<FileResponse>>;
1280
1305
  protected processOenormConversionConvertToOenorm(response: Response): Promise<SwaggerResponse<FileResponse>>;
1281
1306
  }
1282
1307
  export declare class RebConversionApi {
@@ -2578,9 +2603,9 @@ export declare class PositionDto extends IElementDto implements IPositionDto {
2578
2603
  /** A main position means that this position is important and should be highlighted in the user interface. Important meaning that is is usually a bigger part of the total sum of the services, or it needs special attention in another way. */
2579
2604
  isMainPosition: boolean;
2580
2605
  constructor(data?: IPositionDto);
2581
- init?(_data?: any): void;
2606
+ init(_data?: any): void;
2582
2607
  static fromJS(data: any): PositionDto;
2583
- toJSON?(data?: any): any;
2608
+ toJSON(data?: any): any;
2584
2609
  }
2585
2610
  /** A Position is the main item type in a ServiceSpecification, holding information about tasks to be done, their prices, description, amounts etc. */
2586
2611
  export interface IPositionDto extends IIElementDto {
@@ -3352,9 +3377,9 @@ export declare class ExecutionDescriptionDto extends IElementDto implements IExe
3352
3377
  identifier?: string | undefined;
3353
3378
  elementType?: string | undefined;
3354
3379
  constructor(data?: IExecutionDescriptionDto);
3355
- init?(_data?: any): void;
3380
+ init(_data?: any): void;
3356
3381
  static fromJS(data: any): ExecutionDescriptionDto;
3357
- toJSON?(data?: any): any;
3382
+ toJSON(data?: any): any;
3358
3383
  }
3359
3384
  /** An ExecutionDescription is used to give more details for certain items, especially on how they are meant to be executed. */
3360
3385
  export interface IExecutionDescriptionDto extends IIElementDto {
@@ -3393,9 +3418,9 @@ export declare class NoteTextDto extends IElementDto implements INoteTextDto {
3393
3418
  oenormNoteTextProperties?: OenormNoteTextPropertiesDto | undefined;
3394
3419
  readonly hasBidderCommentInHtmlLongText: boolean;
3395
3420
  constructor(data?: INoteTextDto);
3396
- init?(_data?: any): void;
3421
+ init(_data?: any): void;
3397
3422
  static fromJS(data: any): NoteTextDto;
3398
- toJSON?(data?: any): any;
3423
+ toJSON(data?: any): any;
3399
3424
  }
3400
3425
  /** Represents an element that holds text information. */
3401
3426
  export interface INoteTextDto extends IIElementDto {
@@ -3510,9 +3535,9 @@ export declare class ServiceSpecificationGroupDto extends IElementDto implements
3510
3535
  /** This is an optional property that can be used together with AlternativeTo and AlternativeGroupIdentifier. If this is set, you can indicate which alternative group a specific group is assigned to. That way, you can specify the id (in integer format) for the alternative group this group belongs to. It's different to AlternativeIdentifier in that the other property describes the id of the group, while this property here describes the group itself. If a group only has set AlternativeGroupIdentifier but not AlternativeIdentifier, then it likely is a base group for a specific group. This property is not checked or managed automatically, so it is possible for this property to become invalid, by for example setting this property but not setting a base group via AlternativeTo. */
3511
3536
  alternativeGroupIdentifier?: number | undefined;
3512
3537
  constructor(data?: IServiceSpecificationGroupDto);
3513
- init?(_data?: any): void;
3538
+ init(_data?: any): void;
3514
3539
  static fromJS(data: any): ServiceSpecificationGroupDto;
3515
- toJSON?(data?: any): any;
3540
+ toJSON(data?: any): any;
3516
3541
  }
3517
3542
  /** This is a grouping IElement that holds other IElements within. */
3518
3543
  export interface IServiceSpecificationGroupDto extends IIElementDto {