Fixed retext-english usage #44
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
retext-english now provides a Parser object. The previous code will not run with the current version.
|
Sorry for the wait, thanks for your patience. I’ve been working on the releases. The parsers are now no longer exported. I think you can get it from the |
|
Thanks for your patience. I rewrote all guides in 97178c6. See it live here! |
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.
Initial checklist
Description of changes
retext-english now provides a Parser object. The previous code will not run with the current version of retest-english, which will trigger the warning
TypeError: Cannot call a class constructor without |new|in runtime.The solution is import the
Parserobject from the package and use it instead when generating the syntax tree.