@ccf-openapi/ng-client

@ccf-openapi/ng-client@1.2.0

$3

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

$3

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

$3

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

_published:_

`
npm install @ccf-openapi/ng-client@1.2.0 --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 @ccf-openapi/ng-client
`

__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:


`
// without configuring providers
import { CcfApiModule } from '@ccf-openapi/ng-client';
import { HttpClientModule } from '@angular/common/http';

@NgModule({
imports: [
CcfApiModule,
// 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 {}
`

`
// configuring providers
import { CcfApiModule, CcfApiConfiguration, CcfApiConfigurationParameters } from '@ccf-openapi/ng-client';

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

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

`
// configuring providers with an authentication service that manages your access tokens
import { CcfApiModule, CcfApiConfiguration } from '@ccf-openapi/ng-client';

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

`
import { DefaultApi } from '@ccf-openapi/ng-client';

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

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

#### Using multiple OpenAPI files / APIs / CcfApiModules
In order to use multiple CcfApiModules generated from different OpenAPI files,
you can create an alias name when importing the modules
in order to avoid naming conflicts:
`
import { CcfApiModule } from 'my-api-path';
import { CcfApiModule as OtherApiModule } from 'my-other-api-path';
import { HttpClientModule } from '@angular/common/http';

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

}
`

$3

`
import { BASE_PATH } from '@ccf-openapi/ng-client';

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

`
import { BASE_PATH } from '@ccf-openapi/ng-client';

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


#### Using @angular/cli
First extend your src/environments/*.ts files by adding the corresponding base path:

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

In the src/app/app.module.ts:
`
import { BASE_PATH } from '@ccf-openapi/ng-client';
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