GraphQL: Relay version >=0.8.0 introduce ID compatibility issue (objectIdSize higher than 19)

[Moumouls]

New Issue Checklist

• I am not disclosing a vulnerability.
• I am not just asking a question.
• I have searched through existing issues.
• I can reproduce the issue with the latest version of Parse Server.

Issue Description

With an objectId size setting equal or hight than 20 graphql request with an Mongo objectID fails (Invalid code point issue from graphql relay).

Steps to reproduce

Start a server, set objectIdSize to 20, create an object on graphql api, and the mutation return get the objectId and the id (relay). query the graphql api with the objectId. Request will fail.

Actual Outcome

All request fail using a non relay id

Expected Outcome

Non relay id from any size should works

Environment

Parse server with graphql relay >= 0.8.0
5.0.0-alpha.1

graphql-relay should be downgraded to 0.7.0

[parse-github-assistant]

Thanks for opening this issue!

• 🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.

[Moumouls]

A developer with an objectId size higher than 19 need to downgrade parse-server AND SHOULD NOT update his objectID size.

After the parse PR i'll open an issue on graphql-relay to understand what is going wrong with core ID of size 20

[mtrezza]

To which versions of Parse Server does that currently apply?

[Moumouls]

5.0.0-alpha.1

[parseplatformorg]

🎉 This change has been released in version 5.0.0-alpha.9

[parse-github-assistant]

The label block:release cannot be used in combination with block:beta.

[mtrezza]

Closing, via #7627 (merged into alpha), #7722 (merged into beta).

[parseplatformorg]

🎉 This change has been released in version 5.0.0-beta.10

[parseplatformorg]

🎉 This change has been released in version 5.1.0