-
-
Notifications
You must be signed in to change notification settings - Fork 6.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Import Mapping seems to not work with typescript-angular #3149
Comments
👍 Thanks for opening this issue! The team will review the labels and make any necessary changes. |
@filipvh would you like to try and fix this issue? |
@macjohnny I can try. Wanted to make sure that it is an issue and that there isn't a duplicate i couldn't identify. If one would expect it to do what I expect... :-) |
@filipvh - I'm up against this issue as well for the In the case of the Node client generator, these mappings seem to be intentionally obliterated in the constructor. The Angular generators don't clear the importMappings like that. |
I was mistaken about the Angular generators; the abstract class that these TypeScript generators all specialize also clears the initMappings in the constructor. |
@macjohnny @filipvh - I've created a PR that addresses this issue for the Node client generator. It should be a similar fix for the Angular (and other TypeScript) generators. It might be worth putting this change in the abstract class so that all the TS generators can pick it up, but I wanted a small impact crater for now. |
anyone interested in porting #3469 to the abstract typescript generator? |
Bug Report Checklist
Description
I used importMapping in combination with the typescript-angular generator.
Here is a redacted config file:
openapi-generator version
4.0.1
What happens?
What was expected?
Command line used for generation
The text was updated successfully, but these errors were encountered: