This repository was archived by the owner on Aug 9, 2022. It is now read-only.
Fix encoding error #67
Closed
Conversation
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
… so we should replace it with possible fork And it's mandatory change for person who hasn't legacy com.overzealous artifact in local maven repo
Add expected result files
Contributor
Author
|
Please review my PR. |
This pull request was closed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
I applied changes that was did in #63 pull request, but adapt them for current
devbranch.PR was dedicated to addition support of none-ascii character in doc, when the yaml file was show the unicode character using escaping characters instead of show it as is.
Additionally, bumped dependencies versions, as asked of dependency-bot in #29, #53, #65, #66