Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WIP] Migrate to TypeScript #29

Open
wants to merge 22 commits into
base: master
Choose a base branch
from
Open

[WIP] Migrate to TypeScript #29

wants to merge 22 commits into from

Conversation

takuyaa
Copy link
Owner

@takuyaa takuyaa commented Nov 5, 2018

No description provided.

@takuyaa takuyaa self-assigned this Nov 5, 2018
@chigix
Copy link

chigix commented Nov 27, 2019

Waiting for this release

@ghost
Copy link

ghost commented Nov 29, 2019

When will this be merged and released?

@takuyaa
Copy link
Owner Author

takuyaa commented Nov 30, 2019

@chigix @subs1da I would like to know why you want this. This is not a kind of function, so there is no user's merit.
Could you explain your situation or needs?

@chigix
Copy link

chigix commented Nov 30, 2019

@takuyaa TypeScript implementation is attractive. If there could be typescript base code, morphological analyzing could become available for both nodejs and browser usage and building, though it might be still not be covered in the goal of current development.

In addition, I'm using Angular, which is a pioneer project employing TypeScript among the most famous modern frontend solution frameworks. Because there is no sophisticated JavaScript implementation especially for the usage within TypeScript, I have to do Japanese texts parsing and analysis with Server API implementation -- now I'm using the Kuromoji implementation integrated in Elasticsearch, which is actually not good on the view of the cohesion inside one feature development and integration.

@martinheidegger
Copy link

@takuyaa I can not speak for others but I would like to send a new pull request and would like to contribute based on this typescript source code rather than trying to send a javascript pull request that needs to be heavily rebased at another time.

@justinsilvestre
Copy link

This is not a kind of function, so there is no user's merit.

The users benefit from using software that is free of bugs and regularly updated.

In some ways, static typechecking with TypeScript is just like having unit tests. It catches bugs (like null exceptions, "undefined is not a function" errors etc.) and lets developers refactor and write new features faster.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants