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.convert
to sync (it is at least with kuroshiro-analyzer-kuromoji). I would maybe advocate for creating additional functions with aSync
suffix to separate between async and sync return output. Other analyzers will need to support synchronousparse
(i.e.parseSync
) since that's used withinkuroshiro.convert
method: hexenq/kuroshiro-analyzer-kuromoji#6