@vality/--openapi-template@1.0.0

--api-name API This API provides an interface for managing resources within our system. All changes to resource states, including creation, modification, and deletion operations, are carried out through calls to the corresponding API methods. Any third-party applications interacting with our system are considered external client applications and must authenticate appropriately before accessing the API endpoints. We provide a REST API over the HTTP protocol, the schema of which is described in accordance with the [OpenAPI 3][OAS3] standard. Return codes are described by the corresponding HTTP statuses. The platform accepts and returns JSON values in request and response bodies. [OAS3]: https://swagger.io/specification/ ## Content Format Any request to the API must be performed in UTF-8 encoding and with JSON content type specification. `` Content-Type: application/json; charset=utf-8 ` ## Requests Any API method call must be preceded by providing a unique request identifier for the platform client. This ID is passed in the corresponding header of each HTTP request: ` X-Request-ID: RQID-Z08G3EFE5DZ429VVO755BM19D51 ` We require it to be able to track the lifecycle of any individual request in the system when auditing tasks or technical support inquiries demand it. ### Idempotency When making certain requests, you can specify an _idempotency key_ – a unique set of characters to ensure idempotent request processing. ` X-Idempotency-Key: 881D:08BA ` Even if the platform receives multiple requests to perform a specific operation with the same idempotency key value, this operation will be performed _no more than once_. Thus, in the case of temporary network accessibility issues, you can safely resend requests and be confident that operations like resource creation, data updates, or state changes will ultimately be executed only once. The idempotency key should be a unique identifier for the specific operation you\'re attempting to perform. Make sure to use different idempotency keys for different operations.

The version of the OpenAPI document: 1.0.0

Building

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

`console
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:_

`console
npm install @vality/--openapi-template@1.0.0 --save
`

_without publishing (not recommended):_

`console
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:

`console
npm link
`

In your project:

`console
npm link @vality/--openapi-template
`

__Note for Windows users:__ The Angular CLI has troubles to use linked npm packages.
Please refer to this issue for a solution / workaround.
Published packages are not effected by this issue.

$3

In your Angular project:

`typescript
// without configuring providers
import { ApiModule } from '@vality/--openapi-template';
import { HttpClientModule } from '@angular/common/http';

@NgModule({
imports: [
ApiModule,
// make sure to import the HttpClientModule in the AppModule only,
// see https://github.com/angular/angular/issues/20575
HttpClientModule
],
declarations: [ AppComponent ],
providers: [],
bootstrap: [ AppComponent ]
})
export class AppModule {}
`

`typescript
// configuring providers
import { ApiModule, Configuration, ConfigurationParameters } from '@vality/--openapi-template';

export function apiConfigFactory (): Configuration {
const params: ConfigurationParameters = {
// set configuration parameters here.
}
return new Configuration(params);
}

@NgModule({
imports: [ ApiModule.forRoot(apiConfigFactory) ],
declarations: [ AppComponent ],
providers: [],
bootstrap: [ AppComponent ]
})
export class AppModule {}
`

`typescript
// configuring providers with an authentication service that manages your access tokens
import { ApiModule, Configuration } from '@vality/--openapi-template';

@NgModule({
imports: [ ApiModule ],
declarations: [ AppComponent ],
providers: [
{
provide: Configuration,
useFactory: (authService: AuthService) => new Configuration(
{
basePath: environment.apiUrl,
accessToken: authService.getAccessToken.bind(authService)
}
),
deps: [AuthService],
multi: false
}
],
bootstrap: [ AppComponent ]
})
export class AppModule {}
`

`typescript
import { DefaultApi } from '@vality/--openapi-template';

export class AppComponent {
constructor(private apiGateway: DefaultApi) { }
}
`

Note: The ApiModule is restricted to being instantiated once app wide.
This is to ensure that all services are treated as singletons.

$3

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

`typescript
import { ApiModule } from 'my-api-path';
import { ApiModule as OtherApiModule } from 'my-other-api-path';
import { HttpClientModule } from '@angular/common/http';

@NgModule({
imports: [
ApiModule,
OtherApiModule,
// make sure to import the HttpClientModule in the AppModule only,
// see https://github.com/angular/angular/issues/20575
HttpClientModule
]
})
export class AppModule {

}
`

$3

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

`typescript
import { BASE_PATH } from '@vality/--openapi-template';

bootstrap(AppComponent, [
{ provide: BASE_PATH, useValue: 'https://your-web-service.com' },
]);
`

or

`typescript
import { BASE_PATH } from '@vality/--openapi-template';

@NgModule({
imports: [],
declarations: [ AppComponent ],
providers: [ provide: BASE_PATH, useValue: 'https://your-web-service.com' ],
bootstrap: [ AppComponent ]
})
export class AppModule {}
`

$3

First extend your src/environments/*.ts files by adding the corresponding base path:

`typescript
export const environment = {
production: false,
API_BASE_PATH: 'http://127.0.0.1:8080'
};
`

In the src/app/app.module.ts:

`typescript
import { BASE_PATH } from '@vality/--openapi-template';
import { environment } from '../environments/environment';

@NgModule({
declarations: [
AppComponent
],
imports: [ ],
providers: [{ provide: BASE_PATH, useValue: environment.API_BASE_PATH }],
bootstrap: [ AppComponent ]
})
export class AppModule { }
`

$3

Without further customization, only [path-parameters][parameter-locations-url] of [style][style-values-url] '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:

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

[parameter-locations-url]: https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#parameter-locations
[style-values-url]: https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#style-values
[@honoluluhenk/http-param-expander]: https://www.npmjs.com/package/@honoluluhenk/http-param-expander