Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

feature: checking spell and autocorrect spell

See original GitHub issue

checking spell and autocorrect spell

just like write in Page, if you type the wrong word, the recommended words will be shown below.

Steps to reproduce

It’s a new feature.

Versions

Mark Text: master
OS: all platforms.

IssueHunt Summary

fxha has been rewarded.

Backers (Total: $5.00)

boostio ($5.00)

Submitted pull Requests

#1424 Add experimental spellchecker

Tips

Checkout the Issuehunt explorer to discover more funded issues.
Need some help from other developers? Add your repositories on IssueHunt to raise funds.

IssueHunt has been backed by the following sponsors. Become a sponsor

Issue Analytics

State:
Created 5 years ago
Reactions:10
Comments:15 (13 by maintainers)

Top GitHub Comments

3reactions

Jocscommented, Nov 6, 2018

electron-hunspell it looks good, I don’t have a specific idea about which library the spell checker uses, but for the interface, hope is like this. 2018-11-07 1 01 19

1reaction

N-McAcommented, Jan 27, 2019

Another approach to spell checking would be to use an external service like https://languagetool.org ; I spent a while thinking about how to integrate it but the issue I’m running into is how to produce a source map that can indicate where in the editor to show the spelling errors.

It’s not so hard to go from the existing markdown -> html using marked and then extract the text nodes from that to send to the service. Supposing you do this to grab a string, what you get back is a big object of issues, each of which occurs at a location. Getting back from that location to a location in the editor seems non-trivial.

@fxha or @jocs could you provide any ideas as to how to do this?