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

3.0 on @parse/server #4355

Closed
wants to merge 1 commit into from
Closed

3.0 on @parse/server #4355

wants to merge 1 commit into from

Conversation

flovilmart
Copy link
Contributor

No description provided.

@codecov
Copy link

codecov bot commented Nov 16, 2017

Codecov Report

Merging #4355 into 3.x will increase coverage by 0.01%.
The diff coverage is n/a.

Impacted file tree graph

@@            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
Impacted Files Coverage Δ
src/RestWrite.js 93.28% <0%> (+0.18%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c36400a...f6a3297. Read the comment docs.

"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",
Copy link
Contributor

@montymxb montymxb Nov 16, 2017

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.

Copy link
Contributor Author

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.

Copy link
Contributor Author

@flovilmart flovilmart left a 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.

@montymxb
Copy link
Contributor

Alright. Well beyond anything else that needs to be done this looks good for the 3.X line.

@adanski
Copy link

adanski commented Nov 20, 2017

I'd like to ask if there's a roadmap for 3.0. I'm really interested in the upcoming changes.

@montymxb
Copy link
Contributor

@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.?

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

Successfully merging this pull request may close these issues.

3 participants