Skip to content
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

typescript-angular: Allow for custom naming of ApiModule #4209

Merged
merged 1 commit into from
Oct 24, 2019

Conversation

mrmeku
Copy link
Contributor

@mrmeku mrmeku commented Oct 21, 2019

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.sh if 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

Copy link
Member

@macjohnny macjohnny left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your PR!

@mrmeku mrmeku force-pushed the prefix-typescript-angular branch 2 times, most recently from 47f4dda to 9457bb9 Compare October 22, 2019 21:27
In cases where a user wants to generate multiple module's,
it is convenient to have these modules have different names.
@mrmeku mrmeku force-pushed the prefix-typescript-angular branch from 9457bb9 to a0b4105 Compare October 22, 2019 21:35
@macjohnny macjohnny merged commit e85f6c5 into OpenAPITools:master Oct 24, 2019
@wing328 wing328 added this to the 4.2.0 milestone Oct 30, 2019
@wing328
Copy link
Member

wing328 commented Oct 31, 2019

@mrmeku thanks for the PR, which has been included in v4.2.0 release: https://twitter.com/oas_generator/status/1189824932345069569

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[REQ][typescript-angular] Option to rename ApiModule and Configuration
3 participants