ci: Add support for Parse Server 6

[dblythy]

New Pull Request Checklist

• I am not disclosing a vulnerability.
• I am creating this PR in reference to an issue.

Issue Description

SDK does not currently support Parse Server 6, as the startup method has changed.

Closes: #1637

Approach

TODOs before merging

• Add tests

[parse-github-assistant]

Thanks for opening this pull request!

• 🎉 We are excited about your hands-on contribution!

[dblythy]

@mtrezza The SDK should still be compatible with previous versions, it's only the startup method which is a devDependancy that breaks the CI

[codecov]

Codecov Report

Base: 99.89% // Head: 99.89% // No change to project coverage 👍

Coverage data is based on head (88f9e39) compared to base (dfb5196).
Patch coverage: 100.00% of modified lines in pull request are covered.

❗ Current head 88f9e39 differs from pull request most recent head c4f1472. Consider uploading reports for the commit c4f1472 to get more accurate results

Additional details and impacted files

@@           Coverage Diff           @@
##            alpha    #1641   +/-   ##
=======================================
  Coverage   99.89%   99.89%           
=======================================
  Files          61       61           
  Lines        5973     5973           
  Branches     1367     1367           
=======================================
  Hits         5967     5967           
  Misses          6        6           

Impacted Files	Coverage Δ
src/StorageController.react-native.js	100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[dplewis]

@mtrezza Is this ready to merge? I have to copy the startup code to make PR's

[mtrezza]

Looks good!
@dblythy is this ready for merge?

Is this a breaking change? If so, we'd need to compose a note for the changelog.

If this breaks compatibility with Parse Server <6, a compatibility table needs to be added to the README for Parse Server.

[dplewis]

@mtrezza Looks like its linted code and the server is only here for testing. No breaking changes.

[mtrezza]

There is also a change in package lock, that's strange if there are only test and lint changes.

[dplewis]

@mtrezza You can't test against latest of Parse Server without bumping it. In the package-lock.json they are all dev dependencies. dev: true. Dev deps don't affect the build

[mtrezza]

Ah right, we import the alpha branch of Parse Server here, hence the lock file changes. Really not an ideal solution.

Let's think this through once more. So this is actually not a feat commit, but a ci commit, since it's only adapting the tests. If we are adapting the tests for Parse Server 6, we are not testing anymore against Parse Server 5. Since Parse Server 6 has breaking changes, I assume there is a also a chance that the Parse JS SDK becomes incompatible with Parse Server 5 at some point.

It may be problematic that we are only testing with the latest Parse Server alpha branch. If we could add a CI test for at least the latest Parse Server 5 (branch release-5.x.x), we would know when the compatibility breaks.

[mtrezza]

To get ahead here, let's merge this for now and assume the SDK stays compatible with Parse Server 5. We should add Parse Server 5 testing to the CI to verify compatibility, therefore opened #1651.

[parseplatformorg]

🎉 This change has been released in version 4.0.0-beta.1

[parseplatformorg]

🎉 This change has been released in version 4.0.0

[parseplatformorg]

🎉 This change has been released in version 4.0.0-alpha.6