graphql-mesh icon indicating copy to clipboard operation
graphql-mesh copied to clipboard

Fails on Abacus OData schema

Open shishkin opened this issue 1 month ago • 0 comments

Issue workflow progress

Progress of the issue based on the Contributor Workflow

  • [x] 1. The issue provides a reproduction available on Github

Make sure to fork this template and run yarn generate in the terminal.

Please make sure Mesh package versions under package.json matches yours.

  • [x] 2. A failing test has been provided
  • [ ] 3. A local solution has been provided
  • [ ] 4. A pull request is pending review

Describe the bug

I'm trying to generate a schema for Abacus OData endpoint. Abacus is a proprietary ERP system, though it provides a publicly available schema (archived just in case), which I also copied into the failing test. The vendor is using Microsoft tooling for development, so supposedly the source is valid. Also odata2ts can successfully work with the source schema.

Mesh fails with error:

🕸️  Mesh - Abacus 💥 Failed to generate the schema for the source "Abacus"
 Cannot find type with name undefined
🕸️  Mesh 💥 Error: Schemas couldn't be generated successfully. Check for the logs by running Mesh.
    at getMesh (/.../node_modules/@graphql-mesh/runtime/cjs/get-mesh.js:124:15)
    at async Object.handler (/.../node_modules/@graphql-mesh/cli/cjs/index.js:336:53)

To Reproduce Steps to reproduce the behavior:

See failing test.

Expected behavior

Should successfully generate the schema or point to a detailed error at the source.

Environment:

  • OS: MacOS
  • @graphql-mesh/...: latest master
  • NodeJS: v20

Additional context

The OData schema is huge and mesh provides no detailed diagnostics to pinpoint the issue further.

shishkin avatar May 16 '24 14:05 shishkin