Change the search result in the case of multiple fields from list to tuple #82
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.
While working on #81, I noticed another issue in the results of a searching for multiple fields: the
Client.search()
method returns a list of the results. There are situation where it may be convenient to turn that list into a set and in general this works. Note thatEntity
objects are hashable even though they are mutable and that has been made particularly with the intention to allow them to be added as an item to a set.Now:
In the case of searching for multiple fields, turning the result into a set fails, because it is a list of lists with attribute values. The present PR changes this to a list of tuples instead.