Change to sync#74
Open
lvl99 wants to merge 2 commits into
Open
Conversation
kyranet
suggested changes
Jan 6, 2022
kyranet
left a comment
There was a problem hiding this comment.
Random review from a random guy but... I hope it helps 😅
| * @returns {Promise<string>} Promise result of conversion | ||
| */ | ||
| convert(str, options) { | ||
| return Promise.resolve(this.convertSync(str, options)); |
There was a problem hiding this comment.
I believe this should be the following:
Suggested change
| return Promise.resolve(this.convertSync(str, options)); | |
| return Promise.resolve().then(() => this.convertSync(str, options)); |
This is based on what import(...) is transpiled to when targeting CommonJS, and this approach has a few benefits:
- The execution is delayed instead of done immediately (better async I/O).
- If
this.convertSync(str, options)throws, this will cause a promise rejection, currently it throws a sync error, which makes.catch()not work. - Much cleaner than a try/catch using Promise.resolve and Promise.reject.
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
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.
In reference to #50 :
I've made a quick stab at turning kuroshiro (and kuroshiro-analyzer-kuromoji) sync, and I found that the dependency kuromoji has lag when building the data files so requires callback/promise when initialising kuroshiro/kuroshiro-analyzer-kuromoji -- since @hexenq stated that other analyzers need to be async (although I haven't looked at those analyzers nor do I know if they require async
parse), this is not a blocking issue to going sync IMO.My exploration was mainly to see if it is easy enough to change the
kuroshiro.convertto sync (it is at least with kuroshiro-analyzer-kuromoji). I would maybe advocate for creating additional functions with aSyncsuffix to separate between async and sync return output. Other analyzers will need to support synchronousparse(i.e.parseSync) since that's used withinkuroshiro.convertmethod: hexenq/kuroshiro-analyzer-kuromoji#6