Fixed DefaultGenerator.getHandleBars to not use a regex string for the templateDir #8246
Merged
HugoMario merged 1 commit intoswagger-api:3.0.0from Jun 7, 2018
bigtlb:issue-8218
Merged
Fixed DefaultGenerator.getHandleBars to not use a regex string for the templateDir #8246HugoMario merged 1 commit intoswagger-api:3.0.0from bigtlb:issue-8218
HugoMario merged 1 commit intoswagger-api:3.0.0from
bigtlb:issue-8218
Conversation
Windows) path delimiters `\` would be interpreted as escape sequences. replaced `replaceFirest()` with `StringUtils.replaceOnce()` This fixes #8245
|
Hello, thanks for fixing. |
Contributor
|
thanks a lot @bigtlb i'll take a look on it before merge it. @thomas-worm-datev no for rc1, it was already released. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
(in Windows) path delimiters
\would be interpreted as escape sequences for a regex parameter.Replaced
replaceFirst()withStringUtils.replaceOnce()This fixes #8218