Created by: mrmeku
In cases where a user wants to generate multiple module's, it is convenient to have these modules have different names.
This change introduces a new additional property to the typescript-angular generator. The property is named apiModulePrefix and will serve as the prefix for the generated ApiModule class. For example, if apiModulePrefix=MyPrefix were to be set, the generated module would be named MyPrefixApiModule.
The inspiration for this change is that in many projects I contribute to, we generate many ApiModules for different openapi services. Since all of these modules have the same name it forces to developers to use the import { ApiModule as BlahModule } from ... syntax which is slightly annoying and is incompatible with some code inspection tools which expect that all classes have different names.
The change is non breaking and tests have been added.
PR checklist
-
Read the contribution guidelines. -
If contributing template-only or documentation-only changes which will change sample output, build the project before. -
Run the shell script(s) under ./bin/(or Windows batch scripts under.\bin\windows) to update Petstore samples related to your fix. This is important, as CI jobs will verify all generator outputs of your HEAD commit, and these must match the expectations made by your contribution. You only need to run./bin/{LANG}-petstore.sh,./bin/openapi3/{LANG}-petstore.shif updating the code or mustache templates for a language ({LANG}) (e.g. php, ruby, python, etc). -
File the PR against the correct branch: master,4.1.x,5.0.x. Default:master. -
Copy the technical committee to review the pull request if your PR is targeting a particular programming language.
@TiFu (2017/07) @taxpon (2017/07) @sebastianhaas (2017/07) @kenisteward (2017/07) @Vrolijkx (2017/09) @macjohnny (2018/01) @nicokoenig (2018/09) @topce (2018/10) @akehir (2019/07)
fixes #4101 (closed)