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

Use case sensitivity when checking reserved words #351

Merged
merged 1 commit into from
Jun 21, 2018

Conversation

gbrown-ce
Copy link
Contributor

@gbrown-ce gbrown-ce commented Jun 19, 2018

PR checklist

  • Read the contribution guidelines.
  • Ran the shell script under ./bin/ to update Petstore sample so that CIs can verify the change. (For instance, only need to run ./bin/{LANG}-petstore.sh and ./bin/security/{LANG}-petstore.sh if updating the {LANG} (e.g. php, ruby, python, etc) code generator or {LANG} client's mustache templates). Windows batch files can be found in .\bin\windows\.
  • Filed the PR against the correct branch: master, 3.1.x, 4.0.x. Default: master.
  • Copied the technical committee to review the pull request if your PR is targeting a particular programming language.

Description of the PR

Open API generator previously wasn't case sensitive when checking for reserved words in the typescript generator. This will allow us to have the "Package" model in ProductCatalogs without needing to rename anything. Related issue: #349

@TiFu @taxpon @sebastianhaas @kenisteward @Vrolijkx @macjohnny

Motivation
-------------
Open API generator previously wasn't case sensitive when checking for reserved words in the typescript generator. This will allow us to have the "Package" model in ProductCatalogs without needing to rename anything.

Modifications
------------------
Duplicated the C# logic for reserved words (per the @jimschubert from openapitools' suggestion)
@gbrown-ce gbrown-ce closed this Jun 19, 2018
@gbrown-ce gbrown-ce reopened this Jun 19, 2018
@gbrown-ce gbrown-ce closed this Jun 19, 2018
@gbrown-ce gbrown-ce reopened this Jun 19, 2018
@macjohnny
Copy link
Member

@gbrown-ce thanks for the PR! did you re-generate the samples and then result did not change?

@gbrown-ce
Copy link
Contributor Author

@macjohnny correct, there was no change to the output (and no change was expected given the edge case-ness of the code changes)

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.

looks good to me. well documented

@wing328
Copy link
Member

wing328 commented Jun 21, 2018

@macjohnny thanks for reviewing the change.

@gbrown-ce Looks good to me as well. Thanks for the PR.

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

Successfully merging this pull request may close these issues.

None yet

3 participants