Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Neo4j Source Handler: Unable to Use source parameter in .meshrc.yaml #5392

Closed
1 of 4 tasks
hughsername opened this issue May 4, 2023 · 1 comment
Closed
1 of 4 tasks

Comments

@hughsername
Copy link

hughsername commented May 4, 2023

Issue workflow progress

Progress of the issue based on the
Contributor Workflow

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

  1. Fork the example CodeSandbox shown here: https://the-guild.dev/graphql/mesh/docs/handlers/neo4j
  2. Add a file called schema.graphql, and copy the typeDefs shown here in the @neo4j/graphql getting started guide
  3. Add a source: schema.graphql in the .meshrc.yaml config, per the Config API Reference
  4. Run nom run start (mesh dev) and observe error message about BigInt 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.

@ardatan
Copy link
Owner

ardatan commented May 16, 2023

Fixed in 1705cb9

@ardatan ardatan closed this as completed May 16, 2023
This was referenced Apr 30, 2024
This was referenced May 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants