Description
Issue workflow progress
Progress of the issue based on the
Contributor Workflow
- 1. The issue provides a reproduction available on
Github,
Stackblitz
or
CodeSandbox
Make sure to fork this template and run
yarn generate
in the terminal.Please make sure Mesh package versions under
package.json
matches yours.
- 2. A failing test has been provided
- 3. A local solution has been provided
- 4. A pull request is pending review
Describe the bug
When I provide a source:
attribute in .meshrc.yaml
, I am expecting the underlying @neo4j/graphql
package to generate the schema based on the typeDefs I provide in a *.graphql
file.
mesh dev
fails when I provide the example typeDefs provided in the Getting Started example of @neo4j/graphql
.
The precise error is Mesh - Neo4j Failed to generate the schema Error: "BigInt" defined in resolvers, but not in schema
.
To Reproduce Steps to reproduce the behavior:
CodeSandbox link here, forked from example in website documentation
- Fork the example CodeSandbox shown here: https://the-guild.dev/graphql/mesh/docs/handlers/neo4j
- Add a file called
schema.graphql
, and copy the typeDefs shown here in the@neo4j/graphql
getting started guide - Add a
source: schema.graphql
in the.meshrc.yaml
config, per the Config API Reference - Run
nom run start
(mesh dev) and observe error message aboutBigInt
present in resolvers but not schema in terminal.
Expected behavior
mesh dev
should run without error and serve a Yoga interactive GraphQL playground.
Environment:
- OS: Mac OS X / CodeSandbox
@graphql-mesh/cli
: 0.82.35- `@graphql-mesh/neo4j: 0.93.1
- NodeJS: 16.17.0
Additional context
This seems to happen independent of database credentials, but I have tested against a database that is empty, so presence of existing data in the database doesn't seem to affect behavior.
I have created a local database, a database on https://sandbox.neo4j.com, and the demo database shown in the linked code sandbox.
I have also created and verified a graphql-yoga implementation against the same databases using the neo4j/graphql
package directly, and it is working as expected.