-
Notifications
You must be signed in to change notification settings - Fork 82
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
Unexpected results with WeightedRatioScorer #47
Comments
Found an alternative, it's a fork created from FuzzySharp.
//edit
@Saalvage do you accept/want bug reports on your fork? Issues are currently disabled. |
Bug reports - no, the only reason I forked FuzzySharp was to fix/improve upon some aspect which I needed for a different project |
Using the WeightedRatioScorer for two different strings, one of them gives an unexpected result.
Input
+30.0% Damage to Close Enemies [30.01%
+14.3% Damage to Crowd Controlled Enemies [7.5 - 18.0]%
Choices
Results
For some reason
input1
gives+#% Damage
a score of 90. While forInput2
it works as expected and+#% Damage
gets score of 60.Source
Here is the source to reproduce the issue.
Click me
The text was updated successfully, but these errors were encountered: