Skip to content

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

Description

@Moumouls

New Issue Checklist

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

Activity

  1. parse-github-assistant commented on Oct 13, 2021

    @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.
  2. Moumouls commented on Oct 13, 2021

    @Moumouls
    MemberAuthor

    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

  3. changed the title [-]GraphQL: Relay version introduce compatibility ID base 64 issue from version 0.8.0[/-] [+]GraphQL: Relay version >=0.8.0 introduce ID compatibility issue (objectIdSize higher than 19)[/+] on Oct 13, 2021
  4. mtrezza commented on Oct 13, 2021

    @mtrezza
    Member

    To which versions of Parse Server does that currently apply?

  5. Moumouls commented on Oct 13, 2021

    @Moumouls
    MemberAuthor

    5.0.0-alpha.1

  6. parseplatformorg commented on Nov 27, 2021

    @parseplatformorg
    Contributor

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

  7. added
    block:betaNeeds to be resolved before next release on beta branch; remove label afterwards
    block:releaseNeeds to be resolved before next release on release branch; remove label afterwards
    on Nov 27, 2021
  8. parse-github-assistant commented on Nov 27, 2021

    @parse-github-assistant

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

  9. removed
    block:releaseNeeds to be resolved before next release on release branch; remove label afterwards
    on Nov 27, 2021
  10. removed
    block:betaNeeds to be resolved before next release on beta branch; remove label afterwards
    on Feb 12, 2022
  11. mtrezza commented on Feb 12, 2022

    @mtrezza
    Member

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

  12. parseplatformorg commented on Mar 15, 2022

    @parseplatformorg
    Contributor

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

  13. parseplatformorg commented on Mar 18, 2022

    @parseplatformorg
    Contributor

    🎉 This change has been released in version 5.1.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    state:releasedReleased as stable versionstate:released-alphaReleased as alpha versionstate:released-betaReleased as beta versiontype:bugImpaired feature or lacking behavior that is likely assumed

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions