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 UTF-8 charset on writing files #9976

Merged
merged 2 commits into from
Feb 27, 2020

Conversation

valery1707
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: 3.0.0 branch for changes related to OpenAPI spec 3.0. Default: master.
  • Copied the technical committee to review the pull request if your PR is targeting a particular programming language.

Description of the PR

Using the FilesUtils#writeStringToFile(File, String) method leads to use of a user machine's default charset although the writing string has UTF-8 charset.
This behavior will break file's charset for users which machine's default charset is not UTF-8 - Windows users for example.
Furthermore the FilesUtils#writeStringToFile(File, String) method is deprecated after commons-io version 2.5 (2016-04-22) in favor of the FilesUtils#writeStringToFile(File, String, Charset) method.

@HugoMario
Copy link
Contributor

thanks a lot @valery1707 !!

@HugoMario HugoMario merged commit 48bf4a9 into swagger-api:master Feb 27, 2020
@valery1707 valery1707 deleted the write-stringToFile-withUtf8 branch February 28, 2020 10:07
@HugoMario HugoMario added this to the v2.4.13 milestone Apr 2, 2020
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.

None yet

2 participants