We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I don't know what to do about these, there is no obvious answer.
For now I am adding a check that they have the same length, and just returning the left one, but that is pretty clearly flawed.
The text was updated successfully, but these errors were encountered:
I think we'll anyway need to revisit how we handle the data for merging, so this can be part of that.
We could return a list wrapper that knows both lists and lazily checks for equality :)
An entirely different approach would be to only send differences to previous query results, so that there are never duplicates in the merge.
Sorry, something went wrong.
The problem is we don't even have well defined equality.... if we have a list of Map objects, which are each incomplete model representations....
No branches or pull requests
I don't know what to do about these, there is no obvious answer.
For now I am adding a check that they have the same length, and just returning the left one, but that is pretty clearly flawed.
The text was updated successfully, but these errors were encountered: