-
-
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
Deprecation warning on database listen #7624
Comments
Thanks for opening this issue!
|
Why did you consider a deprecation warning to be a bug? |
From my point of view since a developer do not have control on this warning (specifically on mongo ones) it could be a bug. Parse Server need to be up to date about packages recommendations. Here this issue will spam developers CI (if they use some full server restarts) here some example. Feel free to adjusts labels 🙂 |
version: |
A warning message is not a bug. A bug is a broken or impaired functionality, also see the label description. |
okay got it @mtrezza |
Thanks, I have to admit though that these warning messages are annoying to the point that they seem like a bug, so emotionally I agree with you 🙂 |
Closing via #7626 |
Okay thanks @mtrezza for the last few things 🙂 |
New Issue Checklist
Issue Description
Database listen warning
Steps to reproduce
Start a parse server on master branch
Actual Outcome
Mongo listen database warning
Expected Outcome
No deprecation
Environment
5.0.0-alpha.1
Parse server need to listen directly on mongo client, not on the database. Source code of the warning
The text was updated successfully, but these errors were encountered: