avatar image
1
cant get graphQL scheme and docs to work properly
By Created

Hello,

We were successful in creating a user model and authenticating with the login query as written in the documentation. We are able to access some tables, but unable to access some other tables. We get the response written below.

When we create a new table we can't query the new table. Even after merging all sandboxes. We get the response written below.

Request:
{
  allTablename {
    results {
      id
    }
  }
}

Response:
{
  "errors": [
    {
      "extensions": {
        "statusCode": 400
      },
      "message": "Object 'allTablename' is not found'."
    }
  ]
}

Parts of the playground are not working. When you click on docs and on scheme, there is a Javascript error (Uncaught Error: Invalid or incomplete schema, unknown type: FileFilterInput. Ensure that a full introspection query is used in order to build a client schema.)

In all examples we have send the authorization header. So that isn't the problem.

We experience this in all of our apps. Anyone experience the same problems in their apps? Does anyone know how to solve this problem?


Hello,

We were successful in creating a user model and authenticating with the login query as written in the documentation. We are able to access some tables, but unable to access some other tables. We get the response written below.

When we create a new table we can't query the new table. Even after merging all sandboxes. We get the response written below.

Request:
{
  allTablename {
    results {
      id
    }
  }
}

Response:
{
  "errors": [
    {
      "extensions": {
        "statusCode": 400
      },
      "message": "Object 'allTablename' is not found'."
    }
  ]
}

Parts of the playground are not working. When you click on docs and on scheme, there is a Javascript error (Uncaught Error: Invalid or incomplete schema, unknown type: FileFilterInput. Ensure that a full introspection query is used in order to build a client schema.)

In all examples we have send the authorization header. So that isn't the problem.

We experience this in all of our apps. Anyone experience the same problems in their apps? Does anyone know how to solve this problem?

Answers
Sort by:

Please login to reply to the topic.