Skip to content

Conversation

guptasu
Copy link
Contributor

@guptasu guptasu commented Apr 1, 2015

Issue link 577
Fixed the compile time error in the generated code caused due to unescaped new line characters.

Since the description text is not being escaped, if there is a new line character, it will cause a new line to be added to the source code. This can cause compile time error if the new line character is part of a string (e.g. java string) and there is no '+' sign explicitly added to the code. Note: The code was doing escapeText for properties but not for models. This patch fixes that.

…caped new line characters.

Since the description text is not being escaped, if there is a new line character, it will cause a new line to be added to the source code. This can cause compile time error if the new line character is part of a string (e.g. java string) and there is no '+' sign explicitly added to the code. Note: The code was doing escapeText for properties but not for models. This patch fixes that.
@guptasu guptasu changed the title This is a fix for issue: [577](https://github.com/swagger-api/swagger-codegen/issues/577) This is a fix for issue: [#577](https://github.com/swagger-api/swagger-codegen/issues/577) Apr 1, 2015
@guptasu guptasu changed the title This is a fix for issue: [#577](https://github.com/swagger-api/swagger-codegen/issues/577) Fixed the compile time error in the generated code caused due to unescaped new line characters. Apr 1, 2015
fehguy added a commit that referenced this pull request Apr 2, 2015
Fixed the compile time error in the generated code caused due to unescaped new line characters.
@fehguy fehguy merged commit b6be19b into swagger-api:develop_2.0 Apr 2, 2015
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.

2 participants