You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you're still using `AppModule` and haven't [migrated](https://angular.dev/reference/migrations/standalone) yet, you can still import an Angular module:
77
+
```typescript
78
+
import { {{apiModuleClassName}} } from '{{npmName}}';
79
+
```
80
+
75
81
If different from the generated base path, during app bootstrap, you can provide the base path to your service.
76
82
77
83
```typescript
78
84
import { ApplicationConfig } from '@angular/core';
79
85
import { provideHttpClient } from '@angular/common/http';
80
-
import { provideApi } from 'sample-angular-19-0-0';
If you're still using `AppModule` and haven't [migrated](https://angular.dev/reference/migrations/standalone) yet, you can still import an Angular module:
124
77
```typescript
125
-
import { DefaultApi } from'';
126
-
127
-
exportclassAppComponent {
128
-
constructor(privateapiGateway:DefaultApi) { }
129
-
}
78
+
import { ApiModule } from'';
130
79
```
131
80
132
-
Note: The ApiModule is restricted to being instantiated once app wide.
133
-
This is to ensure that all services are treated as singletons.
134
-
135
-
### Using multiple OpenAPI files / APIs / ApiModules
136
-
137
-
In order to use multiple `ApiModules` generated from different OpenAPI files,
138
-
you can create an alias name when importing the modules
139
-
in order to avoid naming conflicts:
81
+
If different from the generated base path, during app bootstrap, you can provide the base path to your service.
0 commit comments