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

[Java] Escaping properties to better handle special characters #628

Merged
merged 4 commits into from
Jul 24, 2018

Conversation

MarvGilb
Copy link
Contributor

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

Currently the CodeGenerator did not escape invalid properties for java and passed them as they are to the created java file. By this, a malformed Java file is generated, that can not be compiled and used. Since json and yaml allow every combination for variables, these need to be escaped and cammelCased.

Fixed header generation. Previously the key was used as value parameter.
Special characters were not escaped for properties and a malformed Java object was created.
Old method from testing
@jmini jmini added this to the 3.1.2 milestone Jul 24, 2018
@jmini jmini merged commit 37be47f into OpenAPITools:master Jul 24, 2018
@wing328 wing328 changed the title [Java] Escaping properties for java. [Java] Escaping properties to better handle special characters Jul 25, 2018
A-Joshi pushed a commit to ihsmarkitoss/openapi-generator that referenced this pull request Feb 27, 2019
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.

3 participants