-
-
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
3.0 on @parse/server #4355
3.0 on @parse/server #4355
Conversation
f8e6ae9
to
f6a3297
Compare
Codecov Report
@@ Coverage Diff @@
## 3.x #4355 +/- ##
==========================================
+ Coverage 92.45% 92.46% +0.01%
==========================================
Files 118 118
Lines 8218 8218
==========================================
+ Hits 7598 7599 +1
+ Misses 620 619 -1
Continue to review full report at Codecov.
|
"name": "parse-server", | ||
"version": "2.6.5", | ||
"name": "@parse/server", | ||
"version": "3.0.0-alpha.0", | ||
"description": "An express module providing a Parse-compatible API server", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we change the description while we're at it? Since this is the server now. Could word it like
An express module for a Parse backend server
Just a thought.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, still can be used as an express app as it’s an express app that can be started.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I need to update README and open PR On docs before we merge.
Alright. Well beyond anything else that needs to be done this looks good for the 3.X line. |
I'd like to ask if there's a roadmap for 3.0. I'm really interested in the upcoming changes. |
@adanski as far as I know not yet but we certainly should! @flovilmart think we could consider setting up a project for 3.0 so we can track upcoming stuff, in-progress, completed, etc.? |
No description provided.