@veeroute/lss-packer-angular 4.7.1599
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.
- package/README.md +156 -0
- package/api/api.d.ts +10 -0
- package/api/convertService.d.ts +44 -0
- package/api/convertServiceInterface.d.ts +28 -0
- package/api/packService.d.ts +162 -0
- package/api/packServiceInterface.d.ts +86 -0
- package/api/systemService.d.ts +63 -0
- package/api/systemServiceInterface.d.ts +30 -0
- package/api.module.d.ts +7 -0
- package/bundles/veeroute-lss-packer-angular.umd.js +1086 -0
- package/bundles/veeroute-lss-packer-angular.umd.js.map +1 -0
- package/cfg/method_groups.json +64 -0
- package/configuration.d.ts +80 -0
- package/encoder.d.ts +11 -0
- package/esm2015/api/api.js +11 -0
- package/esm2015/api/convertService.js +146 -0
- package/esm2015/api/convertServiceInterface.js +2 -0
- package/esm2015/api/packService.js +449 -0
- package/esm2015/api/packServiceInterface.js +2 -0
- package/esm2015/api/systemService.js +165 -0
- package/esm2015/api/systemServiceInterface.js +2 -0
- package/esm2015/api.module.js +33 -0
- package/esm2015/configuration.js +80 -0
- package/esm2015/encoder.js +19 -0
- package/esm2015/index.js +6 -0
- package/esm2015/model/calculationAsyncResult.js +2 -0
- package/esm2015/model/calculationInfo.js +2 -0
- package/esm2015/model/calculationSettings.js +13 -0
- package/esm2015/model/calculationState.js +2 -0
- package/esm2015/model/calculationStatus.js +26 -0
- package/esm2015/model/checkResult.js +13 -0
- package/esm2015/model/coordinates.js +13 -0
- package/esm2015/model/dimensions.js +13 -0
- package/esm2015/model/entityError.js +2 -0
- package/esm2015/model/entityErrorType.js +21 -0
- package/esm2015/model/entityPath.js +2 -0
- package/esm2015/model/entityType.js +23 -0
- package/esm2015/model/entityValidation.js +2 -0
- package/esm2015/model/entityValidationType.js +20 -0
- package/esm2015/model/inlineResponse400.js +2 -0
- package/esm2015/model/inlineResponse401.js +2 -0
- package/esm2015/model/inlineResponse402.js +2 -0
- package/esm2015/model/inlineResponse403.js +2 -0
- package/esm2015/model/inlineResponse404.js +2 -0
- package/esm2015/model/inlineResponse404Detail.js +2 -0
- package/esm2015/model/inlineResponse429.js +2 -0
- package/esm2015/model/inlineResponse500.js +2 -0
- package/esm2015/model/models.js +40 -0
- package/esm2015/model/packResult.js +2 -0
- package/esm2015/model/packSettings.js +2 -0
- package/esm2015/model/packStatistics.js +13 -0
- package/esm2015/model/packTask.js +2 -0
- package/esm2015/model/package.js +2 -0
- package/esm2015/model/packageLayout.js +2 -0
- package/esm2015/model/packageType.js +22 -0
- package/esm2015/model/product.js +2 -0
- package/esm2015/model/productGroupLayout.js +2 -0
- package/esm2015/model/productLayout.js +2 -0
- package/esm2015/model/renderTask.js +2 -0
- package/esm2015/model/schemaError.js +13 -0
- package/esm2015/model/serviceName.js +29 -0
- package/esm2015/model/tracedata.js +2 -0
- package/esm2015/model/unpackedItems.js +13 -0
- package/esm2015/model/validateResult.js +2 -0
- package/esm2015/model/versionResult.js +13 -0
- package/esm2015/variables.js +9 -0
- package/esm2015/veeroute-lss-packer-angular.js +5 -0
- package/fesm2015/veeroute-lss-packer-angular.js +1114 -0
- package/fesm2015/veeroute-lss-packer-angular.js.map +1 -0
- package/index.d.ts +5 -0
- package/model/calculationAsyncResult.d.ts +22 -0
- package/model/calculationInfo.d.ts +30 -0
- package/model/calculationSettings.d.ts +32 -0
- package/model/calculationState.d.ts +24 -0
- package/model/calculationStatus.d.ts +23 -0
- package/model/checkResult.d.ts +20 -0
- package/model/coordinates.d.ts +28 -0
- package/model/dimensions.d.ts +32 -0
- package/model/entityError.d.ts +27 -0
- package/model/entityErrorType.d.ts +18 -0
- package/model/entityPath.d.ts +23 -0
- package/model/entityType.d.ts +20 -0
- package/model/entityValidation.d.ts +27 -0
- package/model/entityValidationType.d.ts +17 -0
- package/model/inlineResponse400.d.ts +37 -0
- package/model/inlineResponse401.d.ts +22 -0
- package/model/inlineResponse402.d.ts +22 -0
- package/model/inlineResponse403.d.ts +22 -0
- package/model/inlineResponse404.d.ts +22 -0
- package/model/inlineResponse404Detail.d.ts +18 -0
- package/model/inlineResponse429.d.ts +22 -0
- package/model/inlineResponse500.d.ts +22 -0
- package/model/models.d.ts +39 -0
- package/model/packResult.d.ts +38 -0
- package/model/packSettings.d.ts +18 -0
- package/model/packStatistics.d.ts +40 -0
- package/model/packTask.d.ts +28 -0
- package/model/package.d.ts +31 -0
- package/model/packageLayout.d.ts +33 -0
- package/model/packageType.d.ts +19 -0
- package/model/product.d.ts +38 -0
- package/model/productGroupLayout.d.ts +29 -0
- package/model/productLayout.d.ts +24 -0
- package/model/renderTask.d.ts +31 -0
- package/model/schemaError.d.ts +24 -0
- package/model/serviceName.d.ts +26 -0
- package/model/tracedata.d.ts +38 -0
- package/model/unpackedItems.d.ts +24 -0
- package/model/validateResult.d.ts +23 -0
- package/model/versionResult.d.ts +28 -0
- package/package.json +27 -0
- package/variables.d.ts +8 -0
- package/veeroute-lss-packer-angular.d.ts +4 -0
- package/veeroute-lss-packer-angular.metadata.json +1 -0
package/README.md
ADDED
|
@@ -0,0 +1,156 @@
|
|
|
1
|
+
## @veeroute/lss-packer-angular@4.7.1599
|
|
2
|
+
|
|
3
|
+
## General usage
|
|
4
|
+
|
|
5
|
+
In your Angular project:
|
|
6
|
+
|
|
7
|
+
|
|
8
|
+
```
|
|
9
|
+
// without configuring providers
|
|
10
|
+
import { LssPackerApiModule } from '@veeroute/lss-packer-angular';
|
|
11
|
+
import { HttpClientModule } from '@angular/common/http';
|
|
12
|
+
|
|
13
|
+
@NgModule({
|
|
14
|
+
imports: [
|
|
15
|
+
LssPackerApiModule,
|
|
16
|
+
// make sure to import the HttpClientModule in the AppModule only,
|
|
17
|
+
// see https://github.com/angular/angular/issues/20575
|
|
18
|
+
HttpClientModule
|
|
19
|
+
],
|
|
20
|
+
declarations: [ AppComponent ],
|
|
21
|
+
providers: [],
|
|
22
|
+
bootstrap: [ AppComponent ]
|
|
23
|
+
})
|
|
24
|
+
export class AppModule {}
|
|
25
|
+
```
|
|
26
|
+
|
|
27
|
+
```
|
|
28
|
+
// configuring providers
|
|
29
|
+
import { LssPackerApiModule, Configuration, ConfigurationParameters } from '@veeroute/lss-packer-angular';
|
|
30
|
+
|
|
31
|
+
export function apiConfigFactory (): Configuration {
|
|
32
|
+
const params: ConfigurationParameters = {
|
|
33
|
+
// set configuration parameters here.
|
|
34
|
+
}
|
|
35
|
+
return new Configuration(params);
|
|
36
|
+
}
|
|
37
|
+
|
|
38
|
+
@NgModule({
|
|
39
|
+
imports: [ LssPackerApiModule.forRoot(apiConfigFactory) ],
|
|
40
|
+
declarations: [ AppComponent ],
|
|
41
|
+
providers: [],
|
|
42
|
+
bootstrap: [ AppComponent ]
|
|
43
|
+
})
|
|
44
|
+
export class AppModule {}
|
|
45
|
+
```
|
|
46
|
+
|
|
47
|
+
```
|
|
48
|
+
// configuring providers with an authentication service that manages your access tokens
|
|
49
|
+
import { LssPackerApiModule, Configuration } from '@veeroute/lss-packer-angular';
|
|
50
|
+
|
|
51
|
+
@NgModule({
|
|
52
|
+
imports: [ LssPackerApiModule ],
|
|
53
|
+
declarations: [ AppComponent ],
|
|
54
|
+
providers: [
|
|
55
|
+
{
|
|
56
|
+
provide: Configuration,
|
|
57
|
+
useFactory: (authService: AuthService) => new Configuration(
|
|
58
|
+
{
|
|
59
|
+
basePath: environment.apiUrl,
|
|
60
|
+
accessToken: authService.getAccessToken.bind(authService)
|
|
61
|
+
}
|
|
62
|
+
),
|
|
63
|
+
deps: [AuthService],
|
|
64
|
+
multi: false
|
|
65
|
+
}
|
|
66
|
+
],
|
|
67
|
+
bootstrap: [ AppComponent ]
|
|
68
|
+
})
|
|
69
|
+
export class AppModule {}
|
|
70
|
+
```
|
|
71
|
+
|
|
72
|
+
```
|
|
73
|
+
import { DefaultApi } from '@veeroute/lss-packer-angular';
|
|
74
|
+
|
|
75
|
+
export class AppComponent {
|
|
76
|
+
constructor(private apiGateway: DefaultApi) { }
|
|
77
|
+
}
|
|
78
|
+
```
|
|
79
|
+
|
|
80
|
+
Note: The LssPackerApiModule is restricted to being instantiated once app wide.
|
|
81
|
+
This is to ensure that all services are treated as singletons.
|
|
82
|
+
|
|
83
|
+
#### Using multiple OpenAPI files / APIs / LssPackerApiModules
|
|
84
|
+
In order to use multiple `LssPackerApiModules` generated from different OpenAPI files,
|
|
85
|
+
you can create an alias name when importing the modules
|
|
86
|
+
in order to avoid naming conflicts:
|
|
87
|
+
```
|
|
88
|
+
import { LssPackerApiModule } from 'my-api-path';
|
|
89
|
+
import { LssPackerApiModule as OtherApiModule } from 'my-other-api-path';
|
|
90
|
+
import { HttpClientModule } from '@angular/common/http';
|
|
91
|
+
|
|
92
|
+
@NgModule({
|
|
93
|
+
imports: [
|
|
94
|
+
LssPackerApiModule,
|
|
95
|
+
OtherApiModule,
|
|
96
|
+
// make sure to import the HttpClientModule in the AppModule only,
|
|
97
|
+
// see https://github.com/angular/angular/issues/20575
|
|
98
|
+
HttpClientModule
|
|
99
|
+
]
|
|
100
|
+
})
|
|
101
|
+
export class AppModule {
|
|
102
|
+
|
|
103
|
+
}
|
|
104
|
+
```
|
|
105
|
+
|
|
106
|
+
|
|
107
|
+
### Set service base path
|
|
108
|
+
If different than the generated base path, during app bootstrap, you can provide the base path to your service.
|
|
109
|
+
|
|
110
|
+
```
|
|
111
|
+
import { BASE_PATH } from '@veeroute/lss-packer-angular';
|
|
112
|
+
|
|
113
|
+
bootstrap(AppComponent, [
|
|
114
|
+
{ provide: BASE_PATH, useValue: 'https://your-web-service.com' },
|
|
115
|
+
]);
|
|
116
|
+
```
|
|
117
|
+
or
|
|
118
|
+
|
|
119
|
+
```
|
|
120
|
+
import { BASE_PATH } from '@veeroute/lss-packer-angular';
|
|
121
|
+
|
|
122
|
+
@NgModule({
|
|
123
|
+
imports: [],
|
|
124
|
+
declarations: [ AppComponent ],
|
|
125
|
+
providers: [ provide: BASE_PATH, useValue: 'https://your-web-service.com' ],
|
|
126
|
+
bootstrap: [ AppComponent ]
|
|
127
|
+
})
|
|
128
|
+
export class AppModule {}
|
|
129
|
+
```
|
|
130
|
+
|
|
131
|
+
|
|
132
|
+
#### Using @angular/cli
|
|
133
|
+
First extend your `src/environments/*.ts` files by adding the corresponding base path:
|
|
134
|
+
|
|
135
|
+
```
|
|
136
|
+
export const environment = {
|
|
137
|
+
production: false,
|
|
138
|
+
API_BASE_PATH: 'http://127.0.0.1:8080'
|
|
139
|
+
};
|
|
140
|
+
```
|
|
141
|
+
|
|
142
|
+
In the src/app/app.module.ts:
|
|
143
|
+
```
|
|
144
|
+
import { BASE_PATH } from '@veeroute/lss-packer-angular';
|
|
145
|
+
import { environment } from '../environments/environment';
|
|
146
|
+
|
|
147
|
+
@NgModule({
|
|
148
|
+
declarations: [
|
|
149
|
+
AppComponent
|
|
150
|
+
],
|
|
151
|
+
imports: [ ],
|
|
152
|
+
providers: [{ provide: BASE_PATH, useValue: environment.API_BASE_PATH }],
|
|
153
|
+
bootstrap: [ AppComponent ]
|
|
154
|
+
})
|
|
155
|
+
export class AppModule { }
|
|
156
|
+
```
|
package/api/api.d.ts
ADDED
|
@@ -0,0 +1,10 @@
|
|
|
1
|
+
export * from './convertService';
|
|
2
|
+
import { ConvertService } from './convertService';
|
|
3
|
+
export * from './convertServiceInterface';
|
|
4
|
+
export * from './packService';
|
|
5
|
+
import { PackService } from './packService';
|
|
6
|
+
export * from './packServiceInterface';
|
|
7
|
+
export * from './systemService';
|
|
8
|
+
import { SystemService } from './systemService';
|
|
9
|
+
export * from './systemServiceInterface';
|
|
10
|
+
export declare const APIS: (typeof ConvertService | typeof PackService | typeof SystemService)[];
|
|
@@ -0,0 +1,44 @@
|
|
|
1
|
+
/**
|
|
2
|
+
* VRt.Packer [PC]
|
|
3
|
+
* Veeroute Packer API. # Description The service is designed to calculate the placement of goods inside specified packages. ## Package types ### Pallet  *Mono pallet* If a pallet is fully equipped with the same product, then such a pallet is called mono-pallet, mono-pallet loading rules: 1. The maximum permissible height of the pallet with the goods laid on it: 1800 mm 1. Maximum permissible weight of the loaded pallet: 650 kg 1. Packages of goods may only be stacked parallel to the pallet walls. 1. It is allowed to rotate packages around the vertical Z axis and only at right angles. 1. To level the height between positions (for placing another pallet on top), empty spaces can be added to the stacking in layers. *Zoned pallet* After the formation of mono-pallets, the remaining part of the goods of the same article is placed on the next pallet, which is divided into zones by means of a cardboard partition in such a way that only one article is placed in each zone, the zones have the following restrictions: 1. Zones are rectangular. 1. The ratio between the sides of the zones can be any. 1. One side of any zone is always in contact with the edge of the pallet. 1. Allowable number of zones on a pallet: from 2 to 6. 1. Each zone is filled according to the rules for filling a mono-pallet. 1. The stacking height of all goods does not exceed 50 mm, so that another pallet can be placed on top of such a pallet. 1. It is allowed to form pallets with different stacking heights for different positions (the difference in heights is more than 50 mm), if these are the top pallets in a stack. ### Mix box  If the steps above fail to place the item in this way, so that the pallet has the required height or weight, mix boxes are used: 1. Mix boxes can only be placed in one layer. 1. In one mix-box there can be different goods, in this case it is divided by partitions similarly to the pallet (the only difference is that the height of the packed goods is not aligned). 1. Mix boxes can be mixed with items on one pallet. 1. One product can be packed in different mix boxes. ### Slot  Loaded pallets are stacked on top of each other, the slot is where the stack of pallets is placed. The slot has no physical body - so the dimensions of the `body` of the slot are zero. ## Coordinate system  The local coordinate system is used to indicate the location of packages and goods, in which the coordinates of a particular object are indicated relative to the near-left lower corner of the parent object, while: * Horizontal plane - **X**, **Y** axes * Vertical - **Z** axis ## Entity relationship diagram 
|
|
4
|
+
*
|
|
5
|
+
* The version of the OpenAPI document: 4.7.1599
|
|
6
|
+
* Contact: servicedesk@veeroute.com
|
|
7
|
+
*
|
|
8
|
+
* NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
|
|
9
|
+
* https://openapi-generator.tech
|
|
10
|
+
* Do not edit the class manually.
|
|
11
|
+
*/
|
|
12
|
+
import { HttpClient, HttpHeaders, HttpResponse, HttpEvent, HttpParameterCodec, HttpContext } from '@angular/common/http';
|
|
13
|
+
import { Observable } from 'rxjs';
|
|
14
|
+
import { Configuration } from '../configuration';
|
|
15
|
+
import { ConvertServiceInterface, RunConvertToGltfRequestParams } from './convertServiceInterface';
|
|
16
|
+
export declare class ConvertService implements ConvertServiceInterface {
|
|
17
|
+
protected httpClient: HttpClient;
|
|
18
|
+
protected basePath: string;
|
|
19
|
+
defaultHeaders: HttpHeaders;
|
|
20
|
+
configuration: Configuration;
|
|
21
|
+
encoder: HttpParameterCodec;
|
|
22
|
+
constructor(httpClient: HttpClient, basePath: string, configuration: Configuration);
|
|
23
|
+
private addToHttpParams;
|
|
24
|
+
private addToHttpParamsRecursive;
|
|
25
|
+
/**
|
|
26
|
+
* Convert (glTF)
|
|
27
|
+
* Used for render of input and output data to the [glTF](https://en.wikipedia.org/wiki/GlTF) format.
|
|
28
|
+
* @param requestParameters
|
|
29
|
+
* @param observe set whether or not to return the data Observable as the body, response or events. defaults to returning the body.
|
|
30
|
+
* @param reportProgress flag to report request and response progress.
|
|
31
|
+
*/
|
|
32
|
+
runConvertToGltf(requestParameters: RunConvertToGltfRequestParams, observe?: 'body', reportProgress?: boolean, options?: {
|
|
33
|
+
httpHeaderAccept?: 'application/octet-stream' | 'application/json';
|
|
34
|
+
context?: HttpContext;
|
|
35
|
+
}): Observable<string>;
|
|
36
|
+
runConvertToGltf(requestParameters: RunConvertToGltfRequestParams, observe?: 'response', reportProgress?: boolean, options?: {
|
|
37
|
+
httpHeaderAccept?: 'application/octet-stream' | 'application/json';
|
|
38
|
+
context?: HttpContext;
|
|
39
|
+
}): Observable<HttpResponse<string>>;
|
|
40
|
+
runConvertToGltf(requestParameters: RunConvertToGltfRequestParams, observe?: 'events', reportProgress?: boolean, options?: {
|
|
41
|
+
httpHeaderAccept?: 'application/octet-stream' | 'application/json';
|
|
42
|
+
context?: HttpContext;
|
|
43
|
+
}): Observable<HttpEvent<string>>;
|
|
44
|
+
}
|
|
@@ -0,0 +1,28 @@
|
|
|
1
|
+
/**
|
|
2
|
+
* VRt.Packer [PC]
|
|
3
|
+
* Veeroute Packer API. # Description The service is designed to calculate the placement of goods inside specified packages. ## Package types ### Pallet  *Mono pallet* If a pallet is fully equipped with the same product, then such a pallet is called mono-pallet, mono-pallet loading rules: 1. The maximum permissible height of the pallet with the goods laid on it: 1800 mm 1. Maximum permissible weight of the loaded pallet: 650 kg 1. Packages of goods may only be stacked parallel to the pallet walls. 1. It is allowed to rotate packages around the vertical Z axis and only at right angles. 1. To level the height between positions (for placing another pallet on top), empty spaces can be added to the stacking in layers. *Zoned pallet* After the formation of mono-pallets, the remaining part of the goods of the same article is placed on the next pallet, which is divided into zones by means of a cardboard partition in such a way that only one article is placed in each zone, the zones have the following restrictions: 1. Zones are rectangular. 1. The ratio between the sides of the zones can be any. 1. One side of any zone is always in contact with the edge of the pallet. 1. Allowable number of zones on a pallet: from 2 to 6. 1. Each zone is filled according to the rules for filling a mono-pallet. 1. The stacking height of all goods does not exceed 50 mm, so that another pallet can be placed on top of such a pallet. 1. It is allowed to form pallets with different stacking heights for different positions (the difference in heights is more than 50 mm), if these are the top pallets in a stack. ### Mix box  If the steps above fail to place the item in this way, so that the pallet has the required height or weight, mix boxes are used: 1. Mix boxes can only be placed in one layer. 1. In one mix-box there can be different goods, in this case it is divided by partitions similarly to the pallet (the only difference is that the height of the packed goods is not aligned). 1. Mix boxes can be mixed with items on one pallet. 1. One product can be packed in different mix boxes. ### Slot  Loaded pallets are stacked on top of each other, the slot is where the stack of pallets is placed. The slot has no physical body - so the dimensions of the `body` of the slot are zero. ## Coordinate system  The local coordinate system is used to indicate the location of packages and goods, in which the coordinates of a particular object are indicated relative to the near-left lower corner of the parent object, while: * Horizontal plane - **X**, **Y** axes * Vertical - **Z** axis ## Entity relationship diagram 
|
|
4
|
+
*
|
|
5
|
+
* The version of the OpenAPI document: 4.7.1599
|
|
6
|
+
* Contact: servicedesk@veeroute.com
|
|
7
|
+
*
|
|
8
|
+
* NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
|
|
9
|
+
* https://openapi-generator.tech
|
|
10
|
+
* Do not edit the class manually.
|
|
11
|
+
*/
|
|
12
|
+
import { HttpHeaders } from '@angular/common/http';
|
|
13
|
+
import { Observable } from 'rxjs';
|
|
14
|
+
import { RenderTaskPacker } from '../model/models';
|
|
15
|
+
import { Configuration } from '../configuration';
|
|
16
|
+
export interface RunConvertToGltfRequestParams {
|
|
17
|
+
renderTaskPacker: RenderTaskPacker;
|
|
18
|
+
}
|
|
19
|
+
export interface ConvertServiceInterface {
|
|
20
|
+
defaultHeaders: HttpHeaders;
|
|
21
|
+
configuration: Configuration;
|
|
22
|
+
/**
|
|
23
|
+
* Convert (glTF)
|
|
24
|
+
* Used for render of input and output data to the [glTF](https://en.wikipedia.org/wiki/GlTF) format.
|
|
25
|
+
* @param requestParameters
|
|
26
|
+
*/
|
|
27
|
+
runConvertToGltf(requestParameters: RunConvertToGltfRequestParams, extraHttpRequestParams?: any): Observable<string>;
|
|
28
|
+
}
|
|
@@ -0,0 +1,162 @@
|
|
|
1
|
+
/**
|
|
2
|
+
* VRt.Packer [PC]
|
|
3
|
+
* Veeroute Packer API. # Description The service is designed to calculate the placement of goods inside specified packages. ## Package types ### Pallet  *Mono pallet* If a pallet is fully equipped with the same product, then such a pallet is called mono-pallet, mono-pallet loading rules: 1. The maximum permissible height of the pallet with the goods laid on it: 1800 mm 1. Maximum permissible weight of the loaded pallet: 650 kg 1. Packages of goods may only be stacked parallel to the pallet walls. 1. It is allowed to rotate packages around the vertical Z axis and only at right angles. 1. To level the height between positions (for placing another pallet on top), empty spaces can be added to the stacking in layers. *Zoned pallet* After the formation of mono-pallets, the remaining part of the goods of the same article is placed on the next pallet, which is divided into zones by means of a cardboard partition in such a way that only one article is placed in each zone, the zones have the following restrictions: 1. Zones are rectangular. 1. The ratio between the sides of the zones can be any. 1. One side of any zone is always in contact with the edge of the pallet. 1. Allowable number of zones on a pallet: from 2 to 6. 1. Each zone is filled according to the rules for filling a mono-pallet. 1. The stacking height of all goods does not exceed 50 mm, so that another pallet can be placed on top of such a pallet. 1. It is allowed to form pallets with different stacking heights for different positions (the difference in heights is more than 50 mm), if these are the top pallets in a stack. ### Mix box  If the steps above fail to place the item in this way, so that the pallet has the required height or weight, mix boxes are used: 1. Mix boxes can only be placed in one layer. 1. In one mix-box there can be different goods, in this case it is divided by partitions similarly to the pallet (the only difference is that the height of the packed goods is not aligned). 1. Mix boxes can be mixed with items on one pallet. 1. One product can be packed in different mix boxes. ### Slot  Loaded pallets are stacked on top of each other, the slot is where the stack of pallets is placed. The slot has no physical body - so the dimensions of the `body` of the slot are zero. ## Coordinate system  The local coordinate system is used to indicate the location of packages and goods, in which the coordinates of a particular object are indicated relative to the near-left lower corner of the parent object, while: * Horizontal plane - **X**, **Y** axes * Vertical - **Z** axis ## Entity relationship diagram 
|
|
4
|
+
*
|
|
5
|
+
* The version of the OpenAPI document: 4.7.1599
|
|
6
|
+
* Contact: servicedesk@veeroute.com
|
|
7
|
+
*
|
|
8
|
+
* NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
|
|
9
|
+
* https://openapi-generator.tech
|
|
10
|
+
* Do not edit the class manually.
|
|
11
|
+
*/
|
|
12
|
+
import { HttpClient, HttpHeaders, HttpResponse, HttpEvent, HttpParameterCodec, HttpContext } from '@angular/common/http';
|
|
13
|
+
import { Observable } from 'rxjs';
|
|
14
|
+
import { CalculationAsyncResultPacker } from '../model/calculationAsyncResult';
|
|
15
|
+
import { CalculationStatePacker } from '../model/calculationState';
|
|
16
|
+
import { PackResultPacker } from '../model/packResult';
|
|
17
|
+
import { ValidateResultPacker } from '../model/validateResult';
|
|
18
|
+
import { Configuration } from '../configuration';
|
|
19
|
+
import { PackServiceInterface, CancelPackCalculationRequestParams, DeletePackResultRequestParams, ReadPackCalculationStateRequestParams, ReadPackResultRequestParams, RunPackCalculationRequestParams, RunPackCalculationAsyncRequestParams, RunPackValidationRequestParams } from './packServiceInterface';
|
|
20
|
+
export declare class PackService implements PackServiceInterface {
|
|
21
|
+
protected httpClient: HttpClient;
|
|
22
|
+
protected basePath: string;
|
|
23
|
+
defaultHeaders: HttpHeaders;
|
|
24
|
+
configuration: Configuration;
|
|
25
|
+
encoder: HttpParameterCodec;
|
|
26
|
+
constructor(httpClient: HttpClient, basePath: string, configuration: Configuration);
|
|
27
|
+
private addToHttpParams;
|
|
28
|
+
private addToHttpParamsRecursive;
|
|
29
|
+
/**
|
|
30
|
+
* Cancel calculation
|
|
31
|
+
* Cancel calculation process by the calculation identifier.
|
|
32
|
+
* @param requestParameters
|
|
33
|
+
* @param observe set whether or not to return the data Observable as the body, response or events. defaults to returning the body.
|
|
34
|
+
* @param reportProgress flag to report request and response progress.
|
|
35
|
+
*/
|
|
36
|
+
cancelPackCalculation(requestParameters: CancelPackCalculationRequestParams, observe?: 'body', reportProgress?: boolean, options?: {
|
|
37
|
+
httpHeaderAccept?: 'application/json';
|
|
38
|
+
context?: HttpContext;
|
|
39
|
+
}): Observable<any>;
|
|
40
|
+
cancelPackCalculation(requestParameters: CancelPackCalculationRequestParams, observe?: 'response', reportProgress?: boolean, options?: {
|
|
41
|
+
httpHeaderAccept?: 'application/json';
|
|
42
|
+
context?: HttpContext;
|
|
43
|
+
}): Observable<HttpResponse<any>>;
|
|
44
|
+
cancelPackCalculation(requestParameters: CancelPackCalculationRequestParams, observe?: 'events', reportProgress?: boolean, options?: {
|
|
45
|
+
httpHeaderAccept?: 'application/json';
|
|
46
|
+
context?: HttpContext;
|
|
47
|
+
}): Observable<HttpEvent<any>>;
|
|
48
|
+
/**
|
|
49
|
+
* Result removal
|
|
50
|
+
* Removal of the planning result by the calculation identifier.
|
|
51
|
+
* @param requestParameters
|
|
52
|
+
* @param observe set whether or not to return the data Observable as the body, response or events. defaults to returning the body.
|
|
53
|
+
* @param reportProgress flag to report request and response progress.
|
|
54
|
+
*/
|
|
55
|
+
deletePackResult(requestParameters: DeletePackResultRequestParams, observe?: 'body', reportProgress?: boolean, options?: {
|
|
56
|
+
httpHeaderAccept?: 'application/json';
|
|
57
|
+
context?: HttpContext;
|
|
58
|
+
}): Observable<any>;
|
|
59
|
+
deletePackResult(requestParameters: DeletePackResultRequestParams, observe?: 'response', reportProgress?: boolean, options?: {
|
|
60
|
+
httpHeaderAccept?: 'application/json';
|
|
61
|
+
context?: HttpContext;
|
|
62
|
+
}): Observable<HttpResponse<any>>;
|
|
63
|
+
deletePackResult(requestParameters: DeletePackResultRequestParams, observe?: 'events', reportProgress?: boolean, options?: {
|
|
64
|
+
httpHeaderAccept?: 'application/json';
|
|
65
|
+
context?: HttpContext;
|
|
66
|
+
}): Observable<HttpEvent<any>>;
|
|
67
|
+
/**
|
|
68
|
+
* Calculation state
|
|
69
|
+
* Read calculation state by the calculation identifier.
|
|
70
|
+
* @param requestParameters
|
|
71
|
+
* @param observe set whether or not to return the data Observable as the body, response or events. defaults to returning the body.
|
|
72
|
+
* @param reportProgress flag to report request and response progress.
|
|
73
|
+
*/
|
|
74
|
+
readPackCalculationState(requestParameters: ReadPackCalculationStateRequestParams, observe?: 'body', reportProgress?: boolean, options?: {
|
|
75
|
+
httpHeaderAccept?: 'application/json';
|
|
76
|
+
context?: HttpContext;
|
|
77
|
+
}): Observable<CalculationStatePacker>;
|
|
78
|
+
readPackCalculationState(requestParameters: ReadPackCalculationStateRequestParams, observe?: 'response', reportProgress?: boolean, options?: {
|
|
79
|
+
httpHeaderAccept?: 'application/json';
|
|
80
|
+
context?: HttpContext;
|
|
81
|
+
}): Observable<HttpResponse<CalculationStatePacker>>;
|
|
82
|
+
readPackCalculationState(requestParameters: ReadPackCalculationStateRequestParams, observe?: 'events', reportProgress?: boolean, options?: {
|
|
83
|
+
httpHeaderAccept?: 'application/json';
|
|
84
|
+
context?: HttpContext;
|
|
85
|
+
}): Observable<HttpEvent<CalculationStatePacker>>;
|
|
86
|
+
/**
|
|
87
|
+
* Getting the result
|
|
88
|
+
* Getting the planning result based on the calculation identifier.
|
|
89
|
+
* @param requestParameters
|
|
90
|
+
* @param observe set whether or not to return the data Observable as the body, response or events. defaults to returning the body.
|
|
91
|
+
* @param reportProgress flag to report request and response progress.
|
|
92
|
+
*/
|
|
93
|
+
readPackResult(requestParameters: ReadPackResultRequestParams, observe?: 'body', reportProgress?: boolean, options?: {
|
|
94
|
+
httpHeaderAccept?: 'application/json';
|
|
95
|
+
context?: HttpContext;
|
|
96
|
+
}): Observable<PackResultPacker>;
|
|
97
|
+
readPackResult(requestParameters: ReadPackResultRequestParams, observe?: 'response', reportProgress?: boolean, options?: {
|
|
98
|
+
httpHeaderAccept?: 'application/json';
|
|
99
|
+
context?: HttpContext;
|
|
100
|
+
}): Observable<HttpResponse<PackResultPacker>>;
|
|
101
|
+
readPackResult(requestParameters: ReadPackResultRequestParams, observe?: 'events', reportProgress?: boolean, options?: {
|
|
102
|
+
httpHeaderAccept?: 'application/json';
|
|
103
|
+
context?: HttpContext;
|
|
104
|
+
}): Observable<HttpEvent<PackResultPacker>>;
|
|
105
|
+
/**
|
|
106
|
+
* Packing (SYNC)
|
|
107
|
+
* Planning the optimal package.
|
|
108
|
+
* @param requestParameters
|
|
109
|
+
* @param observe set whether or not to return the data Observable as the body, response or events. defaults to returning the body.
|
|
110
|
+
* @param reportProgress flag to report request and response progress.
|
|
111
|
+
*/
|
|
112
|
+
runPackCalculation(requestParameters: RunPackCalculationRequestParams, observe?: 'body', reportProgress?: boolean, options?: {
|
|
113
|
+
httpHeaderAccept?: 'application/json';
|
|
114
|
+
context?: HttpContext;
|
|
115
|
+
}): Observable<PackResultPacker>;
|
|
116
|
+
runPackCalculation(requestParameters: RunPackCalculationRequestParams, observe?: 'response', reportProgress?: boolean, options?: {
|
|
117
|
+
httpHeaderAccept?: 'application/json';
|
|
118
|
+
context?: HttpContext;
|
|
119
|
+
}): Observable<HttpResponse<PackResultPacker>>;
|
|
120
|
+
runPackCalculation(requestParameters: RunPackCalculationRequestParams, observe?: 'events', reportProgress?: boolean, options?: {
|
|
121
|
+
httpHeaderAccept?: 'application/json';
|
|
122
|
+
context?: HttpContext;
|
|
123
|
+
}): Observable<HttpEvent<PackResultPacker>>;
|
|
124
|
+
/**
|
|
125
|
+
* Packing (ASYNC)
|
|
126
|
+
* The result can be obtained using the [result](#operation/read_pack_result) method, removing - with [delete](#operation/delete_pack_result).
|
|
127
|
+
* @param requestParameters
|
|
128
|
+
* @param observe set whether or not to return the data Observable as the body, response or events. defaults to returning the body.
|
|
129
|
+
* @param reportProgress flag to report request and response progress.
|
|
130
|
+
*/
|
|
131
|
+
runPackCalculationAsync(requestParameters: RunPackCalculationAsyncRequestParams, observe?: 'body', reportProgress?: boolean, options?: {
|
|
132
|
+
httpHeaderAccept?: 'application/json';
|
|
133
|
+
context?: HttpContext;
|
|
134
|
+
}): Observable<CalculationAsyncResultPacker>;
|
|
135
|
+
runPackCalculationAsync(requestParameters: RunPackCalculationAsyncRequestParams, observe?: 'response', reportProgress?: boolean, options?: {
|
|
136
|
+
httpHeaderAccept?: 'application/json';
|
|
137
|
+
context?: HttpContext;
|
|
138
|
+
}): Observable<HttpResponse<CalculationAsyncResultPacker>>;
|
|
139
|
+
runPackCalculationAsync(requestParameters: RunPackCalculationAsyncRequestParams, observe?: 'events', reportProgress?: boolean, options?: {
|
|
140
|
+
httpHeaderAccept?: 'application/json';
|
|
141
|
+
context?: HttpContext;
|
|
142
|
+
}): Observable<HttpEvent<CalculationAsyncResultPacker>>;
|
|
143
|
+
/**
|
|
144
|
+
* Data validation
|
|
145
|
+
* Checking data before planning.
|
|
146
|
+
* @param requestParameters
|
|
147
|
+
* @param observe set whether or not to return the data Observable as the body, response or events. defaults to returning the body.
|
|
148
|
+
* @param reportProgress flag to report request and response progress.
|
|
149
|
+
*/
|
|
150
|
+
runPackValidation(requestParameters: RunPackValidationRequestParams, observe?: 'body', reportProgress?: boolean, options?: {
|
|
151
|
+
httpHeaderAccept?: 'application/json';
|
|
152
|
+
context?: HttpContext;
|
|
153
|
+
}): Observable<ValidateResultPacker>;
|
|
154
|
+
runPackValidation(requestParameters: RunPackValidationRequestParams, observe?: 'response', reportProgress?: boolean, options?: {
|
|
155
|
+
httpHeaderAccept?: 'application/json';
|
|
156
|
+
context?: HttpContext;
|
|
157
|
+
}): Observable<HttpResponse<ValidateResultPacker>>;
|
|
158
|
+
runPackValidation(requestParameters: RunPackValidationRequestParams, observe?: 'events', reportProgress?: boolean, options?: {
|
|
159
|
+
httpHeaderAccept?: 'application/json';
|
|
160
|
+
context?: HttpContext;
|
|
161
|
+
}): Observable<HttpEvent<ValidateResultPacker>>;
|
|
162
|
+
}
|
|
@@ -0,0 +1,86 @@
|
|
|
1
|
+
/**
|
|
2
|
+
* VRt.Packer [PC]
|
|
3
|
+
* Veeroute Packer API. # Description The service is designed to calculate the placement of goods inside specified packages. ## Package types ### Pallet  *Mono pallet* If a pallet is fully equipped with the same product, then such a pallet is called mono-pallet, mono-pallet loading rules: 1. The maximum permissible height of the pallet with the goods laid on it: 1800 mm 1. Maximum permissible weight of the loaded pallet: 650 kg 1. Packages of goods may only be stacked parallel to the pallet walls. 1. It is allowed to rotate packages around the vertical Z axis and only at right angles. 1. To level the height between positions (for placing another pallet on top), empty spaces can be added to the stacking in layers. *Zoned pallet* After the formation of mono-pallets, the remaining part of the goods of the same article is placed on the next pallet, which is divided into zones by means of a cardboard partition in such a way that only one article is placed in each zone, the zones have the following restrictions: 1. Zones are rectangular. 1. The ratio between the sides of the zones can be any. 1. One side of any zone is always in contact with the edge of the pallet. 1. Allowable number of zones on a pallet: from 2 to 6. 1. Each zone is filled according to the rules for filling a mono-pallet. 1. The stacking height of all goods does not exceed 50 mm, so that another pallet can be placed on top of such a pallet. 1. It is allowed to form pallets with different stacking heights for different positions (the difference in heights is more than 50 mm), if these are the top pallets in a stack. ### Mix box  If the steps above fail to place the item in this way, so that the pallet has the required height or weight, mix boxes are used: 1. Mix boxes can only be placed in one layer. 1. In one mix-box there can be different goods, in this case it is divided by partitions similarly to the pallet (the only difference is that the height of the packed goods is not aligned). 1. Mix boxes can be mixed with items on one pallet. 1. One product can be packed in different mix boxes. ### Slot  Loaded pallets are stacked on top of each other, the slot is where the stack of pallets is placed. The slot has no physical body - so the dimensions of the `body` of the slot are zero. ## Coordinate system  The local coordinate system is used to indicate the location of packages and goods, in which the coordinates of a particular object are indicated relative to the near-left lower corner of the parent object, while: * Horizontal plane - **X**, **Y** axes * Vertical - **Z** axis ## Entity relationship diagram 
|
|
4
|
+
*
|
|
5
|
+
* The version of the OpenAPI document: 4.7.1599
|
|
6
|
+
* Contact: servicedesk@veeroute.com
|
|
7
|
+
*
|
|
8
|
+
* NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
|
|
9
|
+
* https://openapi-generator.tech
|
|
10
|
+
* Do not edit the class manually.
|
|
11
|
+
*/
|
|
12
|
+
import { HttpHeaders } from '@angular/common/http';
|
|
13
|
+
import { Observable } from 'rxjs';
|
|
14
|
+
import { CalculationAsyncResultPacker } from '../model/models';
|
|
15
|
+
import { CalculationStatePacker } from '../model/models';
|
|
16
|
+
import { PackResultPacker } from '../model/models';
|
|
17
|
+
import { PackTaskPacker } from '../model/models';
|
|
18
|
+
import { ValidateResultPacker } from '../model/models';
|
|
19
|
+
import { Configuration } from '../configuration';
|
|
20
|
+
export interface CancelPackCalculationRequestParams {
|
|
21
|
+
id: string;
|
|
22
|
+
}
|
|
23
|
+
export interface DeletePackResultRequestParams {
|
|
24
|
+
id: string;
|
|
25
|
+
}
|
|
26
|
+
export interface ReadPackCalculationStateRequestParams {
|
|
27
|
+
id: string;
|
|
28
|
+
}
|
|
29
|
+
export interface ReadPackResultRequestParams {
|
|
30
|
+
id: string;
|
|
31
|
+
}
|
|
32
|
+
export interface RunPackCalculationRequestParams {
|
|
33
|
+
packTaskPacker: PackTaskPacker;
|
|
34
|
+
}
|
|
35
|
+
export interface RunPackCalculationAsyncRequestParams {
|
|
36
|
+
packTaskPacker: PackTaskPacker;
|
|
37
|
+
}
|
|
38
|
+
export interface RunPackValidationRequestParams {
|
|
39
|
+
packTaskPacker: PackTaskPacker;
|
|
40
|
+
}
|
|
41
|
+
export interface PackServiceInterface {
|
|
42
|
+
defaultHeaders: HttpHeaders;
|
|
43
|
+
configuration: Configuration;
|
|
44
|
+
/**
|
|
45
|
+
* Cancel calculation
|
|
46
|
+
* Cancel calculation process by the calculation identifier.
|
|
47
|
+
* @param requestParameters
|
|
48
|
+
*/
|
|
49
|
+
cancelPackCalculation(requestParameters: CancelPackCalculationRequestParams, extraHttpRequestParams?: any): Observable<{}>;
|
|
50
|
+
/**
|
|
51
|
+
* Result removal
|
|
52
|
+
* Removal of the planning result by the calculation identifier.
|
|
53
|
+
* @param requestParameters
|
|
54
|
+
*/
|
|
55
|
+
deletePackResult(requestParameters: DeletePackResultRequestParams, extraHttpRequestParams?: any): Observable<{}>;
|
|
56
|
+
/**
|
|
57
|
+
* Calculation state
|
|
58
|
+
* Read calculation state by the calculation identifier.
|
|
59
|
+
* @param requestParameters
|
|
60
|
+
*/
|
|
61
|
+
readPackCalculationState(requestParameters: ReadPackCalculationStateRequestParams, extraHttpRequestParams?: any): Observable<CalculationStatePacker>;
|
|
62
|
+
/**
|
|
63
|
+
* Getting the result
|
|
64
|
+
* Getting the planning result based on the calculation identifier.
|
|
65
|
+
* @param requestParameters
|
|
66
|
+
*/
|
|
67
|
+
readPackResult(requestParameters: ReadPackResultRequestParams, extraHttpRequestParams?: any): Observable<PackResultPacker>;
|
|
68
|
+
/**
|
|
69
|
+
* Packing (SYNC)
|
|
70
|
+
* Planning the optimal package.
|
|
71
|
+
* @param requestParameters
|
|
72
|
+
*/
|
|
73
|
+
runPackCalculation(requestParameters: RunPackCalculationRequestParams, extraHttpRequestParams?: any): Observable<PackResultPacker>;
|
|
74
|
+
/**
|
|
75
|
+
* Packing (ASYNC)
|
|
76
|
+
* The result can be obtained using the [result](#operation/read_pack_result) method, removing - with [delete](#operation/delete_pack_result).
|
|
77
|
+
* @param requestParameters
|
|
78
|
+
*/
|
|
79
|
+
runPackCalculationAsync(requestParameters: RunPackCalculationAsyncRequestParams, extraHttpRequestParams?: any): Observable<CalculationAsyncResultPacker>;
|
|
80
|
+
/**
|
|
81
|
+
* Data validation
|
|
82
|
+
* Checking data before planning.
|
|
83
|
+
* @param requestParameters
|
|
84
|
+
*/
|
|
85
|
+
runPackValidation(requestParameters: RunPackValidationRequestParams, extraHttpRequestParams?: any): Observable<ValidateResultPacker>;
|
|
86
|
+
}
|
|
@@ -0,0 +1,63 @@
|
|
|
1
|
+
/**
|
|
2
|
+
* VRt.Packer [PC]
|
|
3
|
+
* Veeroute Packer API. # Description The service is designed to calculate the placement of goods inside specified packages. ## Package types ### Pallet  *Mono pallet* If a pallet is fully equipped with the same product, then such a pallet is called mono-pallet, mono-pallet loading rules: 1. The maximum permissible height of the pallet with the goods laid on it: 1800 mm 1. Maximum permissible weight of the loaded pallet: 650 kg 1. Packages of goods may only be stacked parallel to the pallet walls. 1. It is allowed to rotate packages around the vertical Z axis and only at right angles. 1. To level the height between positions (for placing another pallet on top), empty spaces can be added to the stacking in layers. *Zoned pallet* After the formation of mono-pallets, the remaining part of the goods of the same article is placed on the next pallet, which is divided into zones by means of a cardboard partition in such a way that only one article is placed in each zone, the zones have the following restrictions: 1. Zones are rectangular. 1. The ratio between the sides of the zones can be any. 1. One side of any zone is always in contact with the edge of the pallet. 1. Allowable number of zones on a pallet: from 2 to 6. 1. Each zone is filled according to the rules for filling a mono-pallet. 1. The stacking height of all goods does not exceed 50 mm, so that another pallet can be placed on top of such a pallet. 1. It is allowed to form pallets with different stacking heights for different positions (the difference in heights is more than 50 mm), if these are the top pallets in a stack. ### Mix box  If the steps above fail to place the item in this way, so that the pallet has the required height or weight, mix boxes are used: 1. Mix boxes can only be placed in one layer. 1. In one mix-box there can be different goods, in this case it is divided by partitions similarly to the pallet (the only difference is that the height of the packed goods is not aligned). 1. Mix boxes can be mixed with items on one pallet. 1. One product can be packed in different mix boxes. ### Slot  Loaded pallets are stacked on top of each other, the slot is where the stack of pallets is placed. The slot has no physical body - so the dimensions of the `body` of the slot are zero. ## Coordinate system  The local coordinate system is used to indicate the location of packages and goods, in which the coordinates of a particular object are indicated relative to the near-left lower corner of the parent object, while: * Horizontal plane - **X**, **Y** axes * Vertical - **Z** axis ## Entity relationship diagram 
|
|
4
|
+
*
|
|
5
|
+
* The version of the OpenAPI document: 4.7.1599
|
|
6
|
+
* Contact: servicedesk@veeroute.com
|
|
7
|
+
*
|
|
8
|
+
* NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
|
|
9
|
+
* https://openapi-generator.tech
|
|
10
|
+
* Do not edit the class manually.
|
|
11
|
+
*/
|
|
12
|
+
import { HttpClient, HttpHeaders, HttpResponse, HttpEvent, HttpParameterCodec, HttpContext } from '@angular/common/http';
|
|
13
|
+
import { Observable } from 'rxjs';
|
|
14
|
+
import { CheckResultPacker } from '../model/checkResult';
|
|
15
|
+
import { VersionResultPacker } from '../model/versionResult';
|
|
16
|
+
import { Configuration } from '../configuration';
|
|
17
|
+
import { SystemServiceInterface } from './systemServiceInterface';
|
|
18
|
+
export declare class SystemService implements SystemServiceInterface {
|
|
19
|
+
protected httpClient: HttpClient;
|
|
20
|
+
protected basePath: string;
|
|
21
|
+
defaultHeaders: HttpHeaders;
|
|
22
|
+
configuration: Configuration;
|
|
23
|
+
encoder: HttpParameterCodec;
|
|
24
|
+
constructor(httpClient: HttpClient, basePath: string, configuration: Configuration);
|
|
25
|
+
private addToHttpParams;
|
|
26
|
+
private addToHttpParamsRecursive;
|
|
27
|
+
/**
|
|
28
|
+
* Checking the availability
|
|
29
|
+
* Checking the service availability.
|
|
30
|
+
* @param observe set whether or not to return the data Observable as the body, response or events. defaults to returning the body.
|
|
31
|
+
* @param reportProgress flag to report request and response progress.
|
|
32
|
+
*/
|
|
33
|
+
check(observe?: 'body', reportProgress?: boolean, options?: {
|
|
34
|
+
httpHeaderAccept?: 'application/json';
|
|
35
|
+
context?: HttpContext;
|
|
36
|
+
}): Observable<CheckResultPacker>;
|
|
37
|
+
check(observe?: 'response', reportProgress?: boolean, options?: {
|
|
38
|
+
httpHeaderAccept?: 'application/json';
|
|
39
|
+
context?: HttpContext;
|
|
40
|
+
}): Observable<HttpResponse<CheckResultPacker>>;
|
|
41
|
+
check(observe?: 'events', reportProgress?: boolean, options?: {
|
|
42
|
+
httpHeaderAccept?: 'application/json';
|
|
43
|
+
context?: HttpContext;
|
|
44
|
+
}): Observable<HttpEvent<CheckResultPacker>>;
|
|
45
|
+
/**
|
|
46
|
+
* Getting the service version
|
|
47
|
+
* Getting the service version.
|
|
48
|
+
* @param observe set whether or not to return the data Observable as the body, response or events. defaults to returning the body.
|
|
49
|
+
* @param reportProgress flag to report request and response progress.
|
|
50
|
+
*/
|
|
51
|
+
version(observe?: 'body', reportProgress?: boolean, options?: {
|
|
52
|
+
httpHeaderAccept?: 'application/json';
|
|
53
|
+
context?: HttpContext;
|
|
54
|
+
}): Observable<VersionResultPacker>;
|
|
55
|
+
version(observe?: 'response', reportProgress?: boolean, options?: {
|
|
56
|
+
httpHeaderAccept?: 'application/json';
|
|
57
|
+
context?: HttpContext;
|
|
58
|
+
}): Observable<HttpResponse<VersionResultPacker>>;
|
|
59
|
+
version(observe?: 'events', reportProgress?: boolean, options?: {
|
|
60
|
+
httpHeaderAccept?: 'application/json';
|
|
61
|
+
context?: HttpContext;
|
|
62
|
+
}): Observable<HttpEvent<VersionResultPacker>>;
|
|
63
|
+
}
|
|
@@ -0,0 +1,30 @@
|
|
|
1
|
+
/**
|
|
2
|
+
* VRt.Packer [PC]
|
|
3
|
+
* Veeroute Packer API. # Description The service is designed to calculate the placement of goods inside specified packages. ## Package types ### Pallet  *Mono pallet* If a pallet is fully equipped with the same product, then such a pallet is called mono-pallet, mono-pallet loading rules: 1. The maximum permissible height of the pallet with the goods laid on it: 1800 mm 1. Maximum permissible weight of the loaded pallet: 650 kg 1. Packages of goods may only be stacked parallel to the pallet walls. 1. It is allowed to rotate packages around the vertical Z axis and only at right angles. 1. To level the height between positions (for placing another pallet on top), empty spaces can be added to the stacking in layers. *Zoned pallet* After the formation of mono-pallets, the remaining part of the goods of the same article is placed on the next pallet, which is divided into zones by means of a cardboard partition in such a way that only one article is placed in each zone, the zones have the following restrictions: 1. Zones are rectangular. 1. The ratio between the sides of the zones can be any. 1. One side of any zone is always in contact with the edge of the pallet. 1. Allowable number of zones on a pallet: from 2 to 6. 1. Each zone is filled according to the rules for filling a mono-pallet. 1. The stacking height of all goods does not exceed 50 mm, so that another pallet can be placed on top of such a pallet. 1. It is allowed to form pallets with different stacking heights for different positions (the difference in heights is more than 50 mm), if these are the top pallets in a stack. ### Mix box  If the steps above fail to place the item in this way, so that the pallet has the required height or weight, mix boxes are used: 1. Mix boxes can only be placed in one layer. 1. In one mix-box there can be different goods, in this case it is divided by partitions similarly to the pallet (the only difference is that the height of the packed goods is not aligned). 1. Mix boxes can be mixed with items on one pallet. 1. One product can be packed in different mix boxes. ### Slot  Loaded pallets are stacked on top of each other, the slot is where the stack of pallets is placed. The slot has no physical body - so the dimensions of the `body` of the slot are zero. ## Coordinate system  The local coordinate system is used to indicate the location of packages and goods, in which the coordinates of a particular object are indicated relative to the near-left lower corner of the parent object, while: * Horizontal plane - **X**, **Y** axes * Vertical - **Z** axis ## Entity relationship diagram 
|
|
4
|
+
*
|
|
5
|
+
* The version of the OpenAPI document: 4.7.1599
|
|
6
|
+
* Contact: servicedesk@veeroute.com
|
|
7
|
+
*
|
|
8
|
+
* NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
|
|
9
|
+
* https://openapi-generator.tech
|
|
10
|
+
* Do not edit the class manually.
|
|
11
|
+
*/
|
|
12
|
+
import { HttpHeaders } from '@angular/common/http';
|
|
13
|
+
import { Observable } from 'rxjs';
|
|
14
|
+
import { CheckResultPacker } from '../model/models';
|
|
15
|
+
import { VersionResultPacker } from '../model/models';
|
|
16
|
+
import { Configuration } from '../configuration';
|
|
17
|
+
export interface SystemServiceInterface {
|
|
18
|
+
defaultHeaders: HttpHeaders;
|
|
19
|
+
configuration: Configuration;
|
|
20
|
+
/**
|
|
21
|
+
* Checking the availability
|
|
22
|
+
* Checking the service availability.
|
|
23
|
+
*/
|
|
24
|
+
check(extraHttpRequestParams?: any): Observable<CheckResultPacker>;
|
|
25
|
+
/**
|
|
26
|
+
* Getting the service version
|
|
27
|
+
* Getting the service version.
|
|
28
|
+
*/
|
|
29
|
+
version(extraHttpRequestParams?: any): Observable<VersionResultPacker>;
|
|
30
|
+
}
|
package/api.module.d.ts
ADDED
|
@@ -0,0 +1,7 @@
|
|
|
1
|
+
import { ModuleWithProviders } from '@angular/core';
|
|
2
|
+
import { Configuration } from './configuration';
|
|
3
|
+
import { HttpClient } from '@angular/common/http';
|
|
4
|
+
export declare class LssPackerApiModule {
|
|
5
|
+
static forRoot(configurationFactory: () => Configuration): ModuleWithProviders<LssPackerApiModule>;
|
|
6
|
+
constructor(parentModule: LssPackerApiModule, http: HttpClient);
|
|
7
|
+
}
|