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

[hunspell] learn replacements provided interactively by the user #41

Open
drahnr opened this issue Jun 18, 2020 · 3 comments
Open

[hunspell] learn replacements provided interactively by the user #41

drahnr opened this issue Jun 18, 2020 · 3 comments
Assignees
Labels
enhancement 🦚 New feature or request heavy-duty 🚜 Big features not easy to implement
Projects

Comments

@drahnr
Copy link
Owner

drahnr commented Jun 18, 2020

Summary

Currently the same custom replacement has to be typed over and over again, for no reason.

It would be better to learn one instance and then re-run the checkers with the newly recorded item for the current doc comment and all remaining ones.

Will require some re-thinking,one of the following two:

check all items...

  • lazily in interactive mode, i.e. by moving to an iterator only design.
  • and recheck on every learned item, requires to record all decisions of the user made before

Relvenat files: interactive.rs ,hunspell.rs

@drahnr drahnr added the enhancement 🦚 New feature or request label Jun 18, 2020
@drahnr drahnr added the heavy-duty 🚜 Big features not easy to implement label Jun 26, 2020
@drahnr drahnr added this to In Progress in Overview Jul 8, 2020
@drahnr drahnr moved this from In Progress to To Do in Overview Jul 8, 2020
@drahnr
Copy link
Owner Author

drahnr commented Feb 26, 2021

One optione would to use dashmap to store the user selections and skip follow up corrections. This would be significantly easier if most of it would be done async on demand I think.

@drahnr drahnr mentioned this issue Dec 7, 2021
@drahnr drahnr self-assigned this Jan 5, 2024
@blyxyas
Copy link

blyxyas commented May 15, 2024

This would be so appreciated! In big projects there are lots (dozens and dozens) of instances where words like "config", "JSON", or "IDE" are flagged. It would be nice to keep track of which words have already been discarded as typos and just skip them next time.

@drahnr
Copy link
Owner Author

drahnr commented May 16, 2024

Work has started, but given a surge of lack of time, it's going to take some more time #296 - note that it's a bit more complex than anticipated and requires some additional refactor to work consistently.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement 🦚 New feature or request heavy-duty 🚜 Big features not easy to implement
Projects
Overview
  
To Do
Development

No branches or pull requests

2 participants