parse XSLT stylesheets using libxslt-preferred options #2221
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
|
Code Climate has analyzed commit 2195263 and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 93.3% (80% is the threshold). This pull request will bring the total coverage in the repository to 94.0%. View more on Code Climate. |
flavorjones
deleted the
1940-parse-xslt-stylesheet-using-preferred-options
branch
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.
What problem is this PR intended to solve?
See #1940 where some XSL transformations ended up producing slightly different results from
xsltprocHave you included adequate test coverage?
Yes!
Does this change affect the behavior of either the C or the Java implementations?
This behavior appears to be libxslt-specific, and so the test only runs for CRuby; though the document ends up being parsed with the new options on both implementations.