Graphql Mongo db connector ID failure

[ZachHaber]

I tried to follow the examples (which are out of date, so I tried looking through the different packages to get things working). I managed to get apollo server's playground running queries and mutations, but this error occurs. For some reason mongodb's ObjectId type doesn't seem to be working correctly.
Any help as to why this is happening would be appreciated. I can post the server code that I put together if it helps. I've also tried setting the mongo connector's "convertSession/UserIdToMongoObjectId" to both false and true, and neither helped.

{
  "data": {
    "register": null
  },
  "errors": [
    {
      "message": "ID cannot represent value: { _bsontype: \"ObjectID\", id: <Buffer 5b 9a 87 cb c0 98 4a 69 08 1c c6 d9> }",
      "locations": [
        {
          "line": 2,
          "column": 3
        }
      ],
      "path": [
        "register"
      ],
      "extensions": {
        "code": "INTERNAL_SERVER_ERROR",
        "exception": {
          "stacktrace": [
            "TypeError: ID cannot represent value: { _bsontype: \"ObjectID\", id: <Buffer 5b 9a 87 cb c0 98 4a 69 08 1c c6 d9> }",
            "    at GraphQLScalarType.serializeID [as serialize] (\\node_modules\\graphql\\type\\scalars.js:212:9)",
            "    at completeLeafValue (\\node_modules\\graphql\\execution\\execute.js:641:37)",
            "    at completeValue (\\node_modules\\graphql\\execution\\execute.js:587:12)",
            "    at \\node_modules\\graphql\\execution\\execute.js:500:16",
            "    at <anonymous>",
            "    at process._tickCallback (internal/process/next_tick.js:188:7)"
          ]
        }
      }
    }
  ]
}

[ZachHaber]

I just found out that this was caused by a breaking change in graphql 14.x. And they are looking to fixing it: graphql/graphql-js#1520. Sorry about that.

[williamli]

@ZachHaber any idea what I can do now to get accounts-js working without waiting for an update in graphql side?

[pradel]

@williamli you can use graphql 0.13.x

[williamli]

@pradel does graphql 0.13.x work with Apollo server 2?

[pradel]

Yes it is :)

[TrillCyborg]

@williamli you can provide a type definition for id on your server that will send the String id to your client instead of the ObjectID id. It should look something like this...

const accountMutations = accountsGraphQL.resolvers.Mutation;
const registerMutation = accountMutations.register;

const resolvers = {
  Query: {
    ...,
  },
  Mutation: {
    ...,
    register: async (...args) => {
      const userId = await registerMutation(...args);
      return userId.toString();
    },
  },
  User: {
    id: ({  _id }) => typeof _id === 'string' ? _id : _id.toString();
  },
  LoginResult: {
    sessionId: ({ sessionId }) => sessionId.toString(),
  },
};

[williamli]

@TrillCyborg so basically I need to wrap all calls that returns ID with a .toString()...

I think i will just switch to 0.13 for now until this issue is resolved in 14.x

[TrillCyborg]

@williamli yes, but what I have here is what I'm using. It covers all cases. There's only User.id and LoginResult.sessionId

[williamli]

@TrillCyborg it's working fine, thanks