mock

[artola]

I have the following query, and some troubles to mock it. (using v 3.0.6)

      query trialQuery {
        viewer {
          name
          isHireable
          repository(name: "test") {
            issues(first: 5, orderBy: {field: CREATED_AT, direction: DESC}) {
              pageInfo {
                hasPreviousPage
                hasNextPage
                startCursor
                endCursor
              }
              totalCount
              edges {
                node {
                  id
                  title
                  viewerDidAuthor
                  state
                }
              }
            }
          }
        }
        licenses {
          name
        }
      }
    `;

Situation:

• without licenses part, it is possible to mock it (removing the "viewer"), e.g.:

{
    isHireable: false,
    name: 'martin',
    repository: {
      issues: {
        pageInfo: {
          hasPreviousPage: false,
          hasNextPage: true,
          startCursor:
            'Y3Vyc29yOnYyOpK5MjAxOS0wMS0xNFQxMDowNTo0NSswMTowMM4XxS65',
          endCursor: 'Y3Vyc29yOnYyOpK5MjAxOS0wMS0xNFQxMDowNDo0MyswMTowMM4XxS1p',
        },
        totalCount: 25,
        edges: [
          {
            node: {
              id: 'MDU6SXNzdWUzOTg3OTg1MjE=',
              title: 'test 25',
              viewerDidAuthor: true,
              state: 'OPEN',
            },
          },
...

• I would like to have viewer, as it is more semantic, but especially it is necessary if we want to query multiple resources at once, in the example above, no way to mock licenses.

One more thing, if I try to define variables (global), I get an error:

      query trialQuery($repo: String!, $count: Int, $orderBy: IssueOrder) {
        viewer {
          name
          isHireable
          repository(name: $repo) {
            issues(first: $count, orderBy: $orderBy) {
...

Error: repo variable is not defined on viewer arguments

@estrada9166 Could you please give me some hint?

[estrada9166]

@artola Thanks for creating this issue!!

I'll push soon the fix for the issue with multiple queries on the operation... the result will be something like this:

{
  "viewer": {
    "name": "Henry",
    "isHireable": true,
    "repository": {
      "issues": {
        "pageInfo": {
          "hasPreviousPage": false,
          "hasNextPage": false,
          "startCursor": "OpNaDpLDcAIT",
          "endCursor": null
        },
        "totalCount": 9,
        "edges": [
          {
            "node": {
              "id": "59",
              "title": "kzXciEWiuL",
              "viewerDidAuthor": true,
              "state": "OPEN"
            }
          }
        ]
      }
    }
  },
  "licenses": [
    {
      "name": "Inez"
    },
    {
      "name": "Inez"
    }
  ]
}

That's the expected value, right?

Also, I'll check the one with the arguments to fix it on the same release!

[artola]

@estrada9166 Right, the value shape mimic the query shape. For the record, it is from Github GraphQL API.
I think that this library "should" cover the mocking cases of Github API, then it covers everything.
I use Github example, because it is a kind of standard, leading edge and well known implementation. It makes easier to understand cases.
Your are doing a great, fabulous job.

[estrada9166]

@artola Almost done all the changes needed, missing few things to release it!
PR #67

[estrada9166]

@artola There is a new release with this fix, also you can mock errors like this:

const { errors } = tester.mock({ 
  query, 
  fixture: {
    errors: [
      {
        "message": "Cannot query field \"invalidField\" on type \"FamilyInfo\".",
        "locations": [
          {
            "line": 7,
            "column": 5
          }
        ]
      }
    ]
  }
})

and set fixtures to multiples queries:

   const fixture = {
      data: {
        viewer: {
          name: 'easygraphql'
        },
        licenses: [{
          name: 'Super test'
        }]
      }
    }

    const { viewer, licenses } = tester.mock({
      query,
      fixture
    })

Let me know if it works as expected so we can close this issue and also, #63