Port to tagsoup 0.13. #13
Closed
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
|
patch integrated and new version uploaded to hackage, |
axman6
added a commit
to axman6/hxt
that referenced
this pull request
Dec 16, 2022
Simple typo (took me a long time to realise why a regex including [...\r...] was producing a GenRegex with [&UweSchmidt#9;...] and not [&UweSchmidt#13;...]).
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.
tagsoup 0.13 changed lookupNumericEntity to return a String rather than a Char. This updates hxt-tagsoup to work with that.