-
-
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
LiveQuery not triggering event callbacks when using query.containedIn. #2088
Comments
Can you take a look and see if this still happens on Parse Server 2.2.18? |
I should be able to test this out over the weekend. Stay tuned @hramos. |
@hramos I've repeated the same testing after upgrading to parse-server to 2.2.18. Still the same outcome as documented before (i.e, proposal 'create' and 'proposal' updates are not triggering subscription events when using query.containedIn). |
Any update on this? I have the same problem. |
Updates? Same here on latest parse server and parse js client |
+1 |
@matheusfrozzi did you try on the latest version of parse-server as there's been some work in that area: https://github.com/parse-community/parse-server/releases/tag/2.6.3 |
Closing as released part of 2.6.3, (#4231) |
not working on 3.9.0. though |
bump. is there any regression, it doesn't work on latest |
alright sent a PR #8128 |
LiveQuery not triggering event callbacks when using query.containedIn.
Steps to reproduce
A) Parse database contains following classes:
B) JavaScript nextProps variable contains following
C) Code for Query subscription
E) Change retailPrice in Parse Dashboard from 31 to 30
F) Output from Parse Server (verbose)
G. Subscription 'update' Callback doesn't trigger
H. Remove query.containedIn from query
I) Change retailPrice in Parse Dashboard from 30 back to 31
J) Output from Parse Server (verbose)
K. Subscription 'update' Callback triggers (note: no output from parse server in verbose mode)
L. Demonstrate that query.containedIn works with query.find
M. Console outputs "number of proposals = 2"
Expected Results
See above
Actual Outcome
See above
Environment Setup
Logs/Trace
See above
The text was updated successfully, but these errors were encountered: