You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are utilizing the Suggest method from the WeCantSpell.Hunspell library to generate spelling suggestions based on specific input strings we provide. We have integrated this library into two distinct applications, ensuring that both are supplied with identical input. However, we have observed inconsistencies in the suggestions returned by each application. For instance, when we provide the input "100", one application returns "P100" as a suggestion, while the other returns "A1000". Is it normal for the Suggest method to yield different results when called with the same input in different environments or applications?
Here is the code snippet demonstrating our implementation:
var inputstringList = new List<string> { "A100", "P100", "A100 Truck", "D100 Series" };
var dictionary = WordList.CreateFromWords(inputstringList);
var suggestions = dictionary.Suggest("100");
The text was updated successfully, but these errors were encountered:
That is definitely interesting. It seems stable for multiple calls to Suggest on the same dictionary so the randomness is occurring during word list construction. I think that should definitely be stable.
We are utilizing the Suggest method from the WeCantSpell.Hunspell library to generate spelling suggestions based on specific input strings we provide. We have integrated this library into two distinct applications, ensuring that both are supplied with identical input. However, we have observed inconsistencies in the suggestions returned by each application. For instance, when we provide the input "100", one application returns "P100" as a suggestion, while the other returns "A1000". Is it normal for the Suggest method to yield different results when called with the same input in different environments or applications?
Here is the code snippet demonstrating our implementation:
The text was updated successfully, but these errors were encountered: