-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Add a comment field in queries #8799
Comments
Thanks for opening this issue! |
I assume you mean $comment? Seems like a useful feature, could be implemented like:
For the aggregation pipeline this should be already supported. |
It could be coded by taking 'hint' as an example. |
🎉 This change has been released in version 7.0.0-alpha.23 |
@Meglali20 Could you please take a look at the tests in #8928? After merging, it seems that the tests are flaky, see for example https://github.com/parse-community/parse-server/actions/runs/8238148925/job/22528520534. It's not just that one test, but various comment related tests, so it seems to be a general issue with the test structure. Maybe you need to |
When you said various comment related tests are failing, can you confirm whether all tests are failing or only one test fails and the other succeeds? |
Different comment relates tests were failing, sometimes the comment with count, sometimes other ones. It just seems flaky, see the links. |
I checked the failing workflows and I can see that only one test fails at a time, I think it's because of the profiler not being enabled correctly, I will make a PR with updated tests. |
🎉 This change has been released in version 7.0.0-beta.1 |
🎉 This change has been released in version 7.0.0 |
Hi,
For my clients, I monitor their MongoDB Atlas cluster using the Profiler, which shows a graph of all slow queries.
When I see a slow query, it's hard for me to know where it comes from, in the codebase. We have many coders in many projects that all use the Parse JS SDK.
MongoDB query options have a comment field.
It would be great to have it in Parse.
Thx
Olivier
The text was updated successfully, but these errors were encountered: