support changing tokens in morph plugins #33
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
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.
Currently pre/post morph plugins cannot change the searched tokens since they get a local copy of the token (sTmp) which is only used to determine whether the token word exists or not. Assuming the token word exists in the dictionary, the code uses the original sToken as the searched keyword.
This patch simply makes sToken point to the local sTmp variable (which is controllable from a morph plugin) when the word exists.
When a morph plugin is not present, sTmp is the same as sToken (it is copied from it a few lines above) and this change has no effect.