-
-
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
feat: Support $eq query for liveQuery #7606
Labels
state:released
Released as stable version
state:released-alpha
Released as alpha version
state:released-beta
Released as beta version
type:feature
New feature or improvement of existing feature
Comments
Thanks for opening this issue!
|
3 tasks
Looks related to #7227 (comment) In the discussion, there are ways to do equalTo in LiveQuery without $eq which are linked in the discussion. |
parse-github-assistant
bot
removed
the
type:feature
New feature or improvement of existing feature
label
Oct 5, 2021
This was referenced Jun 2, 2023
🎉 This change has been released in version 6.1.0-alpha.18 |
🎉 This change has been released in version 6.3.0-beta.1 |
🎉 This change has been released in version 6.3.0-alpha.1 |
🎉 This change has been released in version 6.3.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
state:released
Released as stable version
state:released-alpha
Released as alpha version
state:released-beta
Released as beta version
type:feature
New feature or improvement of existing feature
New Feature / Enhancement Checklist
Current Limitation
As per this issue, currently it is not possible to combine
equalTo
clause with any other clauses and vice-versa. After adding support for combiningequalTo
clause with other clauses in Parse-SDK-JS's pr.We need to add support
equalTo
for LiveQuery, so that it triggers correct events for client.Feature / Enhancement Description
We would need to add support for
$eq
query in LiveQuery's matchKeyConstraints.Example Use Case
Alternatives / Workarounds
3rd Party References
The text was updated successfully, but these errors were encountered: