Update version to 0.1.4, add DawgPayload utility class #3
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.
as noted in Version on Npm is higher than Github source code #2, the npm version is 0.1.4 while the Github code is still on 0.1.2. I reverse engineered and backported diffs between 0.1.2 and 0.1.4 releases on npm, now source should reflect published package
for the current interface of
dawgjsisn't really convenient forpymorphy2-related things, it is too low-level. I created new class DawgPayload that provides a high-level wrapper around these. Partly based on Az.ts, partly backported from Az.js, partly summoned from the depths of R'Lyeh.