fix: use UTF-8 encoding in generated translation/messages_*.java files #1271
Conversation
This file contains 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
This makes files easier to read. Input encoding for Java compiler is UTF-8 anyway
Codecov Report
@@ Coverage Diff @@
## master #1271 +/- ##
=========================================
Coverage 68.75% 68.75%
+ Complexity 3855 3854 -1
=========================================
Files 174 174
Lines 16029 16029
Branches 2612 2612
=========================================
Hits 11020 11020
Misses 3777 3777
Partials 1232 1232 |
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.
This makes files easier to read. Input encoding for Java compiler is UTF-8 anyway
As far as I can tell, the produced Java files look good