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.

Sign up for GitHub

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

Jump to bottom

Tweak target spellchecking heuristic #681

Open
nico opened this issue Oct 24, 2013 · 4 comments
Open

Tweak target spellchecking heuristic #681

nico opened this issue Oct 24, 2013 · 4 comments

Comments

@nico
Copy link
Collaborator

nico commented Oct 24, 2013

Currently, ninja suggests a spellchecked target if the edit distance is 3 or less. That works well in many cases, but doesn't in some. This issue is for collecting good and bad examples, then that can be used to decide on some better heuristic in the future.

Good: content_unit_tests -> content_unittests
Bad: pdf -> wtf

(to be continued…)
@nico
Copy link
Collaborator Author

nico commented Oct 24, 2013

Good: resource.pak -> resources.pak

@nico
Copy link
Collaborator Author

nico commented Oct 24, 2013

Good: unittests.exe -> unit_tests.exe

(Tacking on ".exe" on windows might be useful)

@nico
Copy link
Collaborator Author

nico commented Oct 31, 2013

Bad: didn't correct "webkit_all" to "all_webkit"

@nico
Copy link
Collaborator Author

nico commented Dec 29, 2013

Bad: unknown target '0j2', did you mean 'not'?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nico