-
Notifications
You must be signed in to change notification settings - Fork 29
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
use filter key for query to fix warning #224
Conversation
positional arguments for 'where' clause is deprecated and results in a warning. the new syntax is documented here: 'https://cloud.google.com/firestore/docs/query-data/queries#python_1'
@AxeemHaider could you help me with the next steps on getting this merged in if it's good? |
Hi @jessicamann! Thank you for your PR! I may suggest you to make sure that the version of "google-cloud-firestore" specified in |
Ah, got it, I'll double check. |
@ADR-007 the existing version constraint works with the change. |
I'm not able to run the test suite that comes with the repo, however (I don't have a separate GCP project that I can use for testing). Would you be able to help with running that? I just ran this change by linking the updated package code to my own repo that is using the fireo dependency. |
+1, thank you |
@ADR-007 thank you for the approval! It looks like only maintainers can merge the pull request. Let me know if there's anything else I can do to help this along. Thanks for taking a look 🙏🏻 |
any chance we can get this merged in? I would love to clean up my logs and reduce some noice. |
I just fixed the CI. Could you please pull latest |
@ADR-007 just pulled the latest from |
Hi @AxeemHaider, could you please take a look on this:
|
@AxeemHaider thanks so much for merging this is in! what are the next steps for cutting a new release? |
@markConklin it's available you can update to version 2.2.2 |
@ADR-007 The authentication failure issue is caused by restrictions from GitHub, which prevent the use of GCP resources for pull requests. If we remove this security measure, automatic tests will run on every pull request. This could allow malicious users to submit resource-intensive pull requests, leading to increased GCP charges. However, we can mitigate this risk by modifying our workflow: tests should only run on pull requests that have been approved by a reviewer. This way, we ensure that only legitimate changes trigger the tests. Currently, I am unsure how to implement this change, but it seems like a viable solution. |
positional arguments for 'where' clause is deprecated and results in a warning. the new syntax is documented here:
'https://cloud.google.com/firestore/docs/query-data/queries#python_1'
This address Issue #220