New issue
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
Query Backfill Features #8791
Query Backfill Features #8791
Conversation
apis/Google.Cloud.Datastore.V1/Google.Cloud.Datastore.V1.IntegrationTests/DatastoreDbTest.cs
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay, now that we know the behavior, please could you modify the documentation comments for the parameters to Filter.In
and Filter.NotIn
so that users can know what to expect if the value is null?
apis/Google.Cloud.Datastore.V1/Google.Cloud.Datastore.V1.IntegrationTests/DatastoreDbTest.cs
Outdated
Show resolved
Hide resolved
I've tried running the tests, and they fail with errors of:
So I think we should instead change the implementation to prevent callers from providing a null argument to start with. |
apis/Google.Cloud.Datastore.V1/Google.Cloud.Datastore.V1.IntegrationTests/DatastoreDbTest.cs
Outdated
Show resolved
Hide resolved
apis/Google.Cloud.Datastore.V1/Google.Cloud.Datastore.V1/FilterPartial.cs
Outdated
Show resolved
Hide resolved
apis/Google.Cloud.Datastore.V1/Google.Cloud.Datastore.V1.IntegrationTests/DatastoreDbTest.cs
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right, this looks appropriate now. I suggest you put it into a single commit with a suitable comment, edit the PR title for posterity, then we can merge.
No description provided.