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
Is the list of object in response["results"] guaranteed to correspond to the order of the matches in the query? It seems to be, but it would be nice (for client code) if we committed to guaranteeing this.
Also (given that floating point comparisons to the "score" field may make people squeamish), it might be nice to return a boolean "ambiguous" for each match.
The text was updated successfully, but these errors were encountered:
Come to think of it...
we might want (in future versions of the API) to return the results as an object with the query strings as the keys. The order is trickier to deal with when some names do not match.
nevermind about the "floating point comparisons" part of the ambiguous bool comment. ambiguous could be true even if the score is 1.0, right? (based on the doc's usage of ambiguous).
Is the list of object in
response["results"]
guaranteed to correspond to the order of the matches in the query? It seems to be, but it would be nice (for client code) if we committed to guaranteeing this.Also (given that floating point comparisons to the "score" field may make people squeamish), it might be nice to return a boolean "ambiguous" for each match.
The text was updated successfully, but these errors were encountered: