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

Suggest closest matching strategy when mispelled #170

Closed
bartoszmajsak opened this Issue Sep 19, 2017 · 0 comments

Comments

Projects
None yet
1 participant
@bartoszmajsak
Member

bartoszmajsak commented Sep 19, 2017

Issue Overview

Currently, we fail when we can't find a strategy. See #167 for details.

Expected Behaviour

Based on https://en.wikipedia.org/wiki/Levenshtein_distance we can suggest matching strategy.

Did you mean changed instead of cahnged?.

Current Behaviour

Failing with an error.

Steps To Reproduce
  1. misspell strategy when configuring the build
  2. run the build
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment