[BaseConnection] fix edge.cursor mismatch.

[thenamankumar]

The cursor for each node generated by the BaseConnection does not match with the start and end cursors generated by Sequelize Pagination.

Check the implementation of the package and replicate/fix the logic of generating cursor in the BaseConnection to match the start and end cursors.

[bharath-123]

Hey I would like to work on this. I am beginning work on this.

[bharath-123]

How can I go about reproducing this issue?

[thenamankumar]

For reproducing the issue, make the following query using the graphql playground at `localhost:3000/api/graphql

users {
  edges {
    node {
      id
    }
    cursor
  }
  pageInfo {
    startCursor
    endCursor
  }
}

You will see that the startCursor won't be same at edges[0].cursor and edges[<last_index].cursor won't be same as endCursor.

[coderrsid]

I don't have oneauth local setup, i am using ONEAUTH_CLIENT_ID, ONEAUTH_CLIENT_SECRET by creating the instance by second method in my env file

[jugshaurya]

@hereisnaman, users are coming to be null even if I have seeded the users? can u tell me why?
should I pass some headers?

User table data: -

Also working on this issue

[thenamankumar]

@jugshaurya try setting withCredentials as true in the gql playground settings.

[jugshaurya]

@jugshaurya try setting withCredentials as true in the gql playground settings.

yes, that worked thanks. Working on the issue now