display multiple suggestions when a config has an unknown feature #1062
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixes : #1061
We use a Levenshtein distance to find the most similar real feature but we also use the npm package names to find entries. This makes it possible to encounter this edge case :
postcss-oklab-function
@csstools/postcss-oklab-function
oklab-function
postcss-lab-function
This is the most similar result because only two characters need to be altered.
Whereas the right result requires at least 8 changes.
This can not be fixed in a general, yet simple way.
Instead of showing only the top hit we will now show the 3 most likely features.
This makes it possible for users to pick the correct option even when a Levenshtein distance gives an unexpected result.