bug(#3864): unhexing via XSL #3901
Merged
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
|
@yegor256 please check |
|
@yegor256 Hey there! 👋 Thanks for your review! You've earned +4 points, which is the minimum reward. Here's the breakdown: +4 base points, -24 for self-review, -10 for having less than 6 comments, and +34 to reach the minimum. Remember, more hits-of-code and comments can boost your score next time! Your current balance is -258. Keep up the good work! 💪 |
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.
Ref: #3864
In this PR I tried to implement unhexing mechanism in pure XSL and used it instead of
StUnhex. In theory it should increase the speed of converting to PHI because of absence ofXMLDocument#xpathmethod calling