Skip to content
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 ClassNames #4544

Closed
kaevee opened this issue Feb 5, 2018 · 5 comments
Closed

LiveQuery ClassNames #4544

kaevee opened this issue Feb 5, 2018 · 5 comments

Comments

@kaevee
Copy link

kaevee commented Feb 5, 2018

We have a project where the client creates arbitrary classes at runtime. We are restarting the services periodically(if need) to reconfigure the live query server.

Is there a way where we can reconfigure the live query server at run time by adding and deleting classes?

@flovilmart
Copy link
Contributor

At the moment it’s not possible due to the current architecture of the server and the live query server. However, what we could easily introduce is a pattern matching option to the list of liveQueryClasses, this way, you could perhaps use a common prefix in your class name and they would automatically match when they’re added by your clients.

@kaevee
Copy link
Author

kaevee commented Feb 5, 2018

Adding pattern matching would be great. It will solve our problems. I have very little experience in Parse server development. I will explore the sources. If you have any suggestions, it would be very helpful.

@flovilmart
Copy link
Contributor

flovilmart commented Feb 5, 2018

Have a look here: https://github.com/parse-community/parse-server/blob/master/src/Controllers/LiveQueryController.js#L35

Instead of checking if the array contains the object, we could check for patterns.

@flovilmart flovilmart reopened this Feb 5, 2018
@kaevee
Copy link
Author

kaevee commented Feb 5, 2018

We did not expect a solution that is clean and straightforward at one go. We will make changes. Thanks again.

@stale
Copy link

stale bot commented Sep 18, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants