@veeroute/[email protected]

Programming interface for the Veeroute Monitor tool. # Description The server side of Veeroute Monitor. Main responsibilities: - storage and processing of waves (input data for planning and trips with their execution results) - recalculation of trips during their execution - creation and storage of statistics on trip execution results - creation and storage of trip execution forecasts ## Trip state model | State code | Description | Expected action | |:-------------|:---------------------------------------------------------|:-------------------------------------------------| | FREE | Trip created, crew not assigned | Operator will assign a crew | | ASSIGNED | Crew assigned | Operator will send the assignment to the crew | | SENT | Assignment sent to the crew | Crew will confirm receipt | | RECEIVED | Crew received the trip (fact TRIP_RECEIVED) | Crew will accept or reject the trip | | CONFIRMED | Crew agreed to perform the trip (fact TRIP_CONFIRMED) | Crew will start performing the trip | | REJECTED | Crew refused to perform the trip (fact TRIP_REJECTED) | Operator will assign a new crew or cancel | | EXECUTING | Crew is performing the trip (fact TRIP_EXECUTING) | Crew will finish all tasks | | FINISHED | Trip is finished — no work is left for the trip | This is a terminal status | | CANCELLED | Trip cancelled by the operator | This is a terminal status | State transitions: Operator: FREE → ASSIGNED → SENT Crew: RECEIVED → CONFIRMED / REJECTED → EXECUTING Conditions: EXECUTING → FINISHED / CANCELLED ## Entity diagram

The version of the OpenAPI document: 7.39.3350

Building

To install the required dependencies and to build the typescript sources run:

npm install
npm run build

Publishing

First build the package then run npm publish dist (don't forget to specify the dist folder!)

Consuming

Navigate to the folder of your consuming project and run one of next commands.

published:

npm install @veeroute/[email protected] --save

without publishing (not recommended):

npm install PATH_TO_GENERATED_PACKAGE/dist.tgz --save

It's important to take the tgz file, otherwise you'll get trouble with links on windows

using npm link:

In PATH_TO_GENERATED_PACKAGE/dist:

npm link

In your project:

npm link @veeroute/lss-monitor-angular

Note for Windows users: The Angular CLI has troubles to use linked npm packages. Please refer to this issue https://github.com/angular/angular-cli/issues/8284 for a solution / workaround. Published packages are not effected by this issue.

General usage

In your Angular project:

import { ApplicationConfig } from '@angular/core';
import { provideHttpClient } from '@angular/common/http';
import { provideApi } from '@veeroute/lss-monitor-angular';

export const appConfig: ApplicationConfig = {
    providers: [
        // ...
        provideHttpClient(),
        provideApi()
    ],
};

NOTE If you're still using AppModule and haven't migrated yet, you can still import an Angular module:

import { LssMonitorApiModule } from '@veeroute/lss-monitor-angular';

If different from the generated base path, during app bootstrap, you can provide the base path to your service.

import { ApplicationConfig } from '@angular/core';
import { provideHttpClient } from '@angular/common/http';
import { provideApi } from '@veeroute/lss-monitor-angular';

export const appConfig: ApplicationConfig = {
    providers: [
        // ...
        provideHttpClient(),
        provideApi('http://localhost:9999')
    ],
};

// with a custom configuration
import { ApplicationConfig } from '@angular/core';
import { provideHttpClient } from '@angular/common/http';
import { provideApi } from '@veeroute/lss-monitor-angular';

export const appConfig: ApplicationConfig = {
    providers: [
        // ...
        provideHttpClient(),
        provideApi({
            withCredentials: true,
            username: 'user',
            password: 'password'
        })
    ],
};

// with factory building a custom configuration
import { ApplicationConfig } from '@angular/core';
import { provideHttpClient } from '@angular/common/http';
import { provideApi, Configuration } from '@veeroute/lss-monitor-angular';

export const appConfig: ApplicationConfig = {
    providers: [
        // ...
        provideHttpClient(),
        {
            provide: Configuration,
            useFactory: (authService: AuthService) => new Configuration({
                    basePath: 'http://localhost:9999',
                    withCredentials: true,
                    username: authService.getUsername(),
                    password: authService.getPassword(),
            }),
            deps: [AuthService],
            multi: false
        }
    ],
};

Using multiple OpenAPI files / APIs

In order to use multiple APIs generated from different OpenAPI files, you can create an alias name when importing the modules in order to avoid naming conflicts:

import { provideApi as provideUserApi } from 'my-user-api-path';
import { provideApi as provideAdminApi } from 'my-admin-api-path';
import { HttpClientModule } from '@angular/common/http';
import { environment } from '../environments/environment';

export const appConfig: ApplicationConfig = {
    providers: [
        // ...
        provideHttpClient(),
        provideUserApi(environment.basePath),
        provideAdminApi(environment.basePath),
    ],
};

Customizing path parameter encoding

Without further customization, only path-parameters of style 'simple' and Dates for format 'date-time' are encoded correctly.

Other styles (e.g. "matrix") are not that easy to encode and thus are best delegated to other libraries (e.g.: @honoluluhenk/http-param-expander).

To implement your own parameter encoding (or call another library), pass an arrow-function or method-reference to the encodeParam property of the Configuration-object (see General Usage above).

Example value for use in your Configuration-Provider:

new Configuration({
    encodeParam: (param: Param) => myFancyParamEncoder(param),
})