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

Non-standard schema filenames don't work (always schema.graphql) #1139

Closed
grrowl opened this issue Sep 27, 2024 · 1 comment · Fixed by #1143
Closed

Non-standard schema filenames don't work (always schema.graphql) #1139

grrowl opened this issue Sep 27, 2024 · 1 comment · Fixed by #1143

Comments

@grrowl
Copy link

grrowl commented Sep 27, 2024

Screenshot

> graffle --schema api/learn/generated-schema.graphql --output api/learn/upstream

node:internal/process/esm_loader:34
      internalBinding('errors').triggerUncaughtException(
                                ^

[Error: ENOENT: no such file or directory, open 'api/learn/schema.graphql'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: 'api/learn/schema.graphql'
}

Node.js v20.11.0

Description

Passing --schema some/folder/file.graphql always attempts to load some/folder/schema.graphql

@jasonkuhrt
Copy link
Member

jasonkuhrt commented Sep 27, 2024

Thanks @grrowl, I spent some time overhauling the generator that was in bad shape. I got new tests started to cover it as well. So for example tests cover that this issue is fixed. Thanks for the feedback!

@jasonkuhrt jasonkuhrt unpinned this issue Sep 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants