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
{{ message }}
This repository has been archived by the owner on May 1, 2023. It is now read-only.
findBestMatch is really cool, but it could use one extra layer of convenience....
You see...I have an array of objects, and one of the attributes is the string that I am comparing.
I need to find the object from the array with the best matching string.
As it is, I have to extract the strings from all objects, find the best matching string, and then go back and find the object whose string is the best matching string.
It would be easier for me to pass-in the list of objects, along with the name of the attribute, and get back a reference to the best object. I suspect that this pattern of usage might be very common.
Again, this is not a bug, just a suggestion to make the API easier to use.
Thanks for this software -- I am going to use it to solve a tricky problem in converting some very old insurance data.
The text was updated successfully, but these errors were encountered:
Hi, sorry, but I'm not inclined towards including that.
Though it would be useful, it's something that should be built by composing this library and whatever logic you require (and even utility functions such as lodash etc).
One of my objectives is to keep the API of this library super simple and stable.
findBestMatch is really cool, but it could use one extra layer of convenience....
You see...I have an array of objects, and one of the attributes is the string that I am comparing.
I need to find the object from the array with the best matching string.
As it is, I have to extract the strings from all objects, find the best matching string, and then go back and find the object whose string is the best matching string.
It would be easier for me to pass-in the list of objects, along with the name of the attribute, and get back a reference to the best object. I suspect that this pattern of usage might be very common.
Again, this is not a bug, just a suggestion to make the API easier to use.
Thanks for this software -- I am going to use it to solve a tricky problem in converting some very old insurance data.
The text was updated successfully, but these errors were encountered: