-
-
Notifications
You must be signed in to change notification settings - Fork 676
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
Generated Resolvers Output file names are undefined for some model names #1690
Comments
I am having the same issue. In my case, the entity name is "Company."
|
Please show a minimal reproducible Prisma schema for this issue |
Hey @MichalLytek you can try with this repo. It has the same issue. |
@MichalLytek I've also submitted an issue in typegraphql-prisma According to @jessekrubin s comment and the changelog for the new prisma release, a new, top-level Prisma Client query, The result is that the generator will try to create an import for an output type for that resolver from Edit: although the issues seem similar, the timing on is a bit off, @BilalGumus wrote the issue before the 5.14.0 release was out, so his problem might be completely unrelated. |
Just add override on your package.json until the corretion of typegraphql
|
If anyone stumbles upon this -- this comment here is what worked for me (I use yarn): MichalLytek/typegraphql-prisma#450 (comment) |
Describe the Bug
When using the
npx prisma generate
command, file names become undefined for models containing 'Integration' or 'Integrate' in their names atgenerated/type-graphql/resolvers/outputs/
.To Reproduce
(e.g. UserIntegration)
npx prisma generate
command.generated/type-graphql/resolvers/outputs/index.ts
.Expected Behavior
The output files should have properly defined names for models containing 'Integration' or 'Integrate'.
Logs
If you create 2 models models with names containing 'Integration' or 'Integrate', during runtime, typescript throws a "duplicate identifier" error for exports. Otherwise you do not get any error.
Environment (please complete the following information):
Additional Context
This bug seems to affect the generation process under specific circumstances, particularly when model names include certain keywords like 'Integration' or 'Integrate'. Especially if there is more than one model name fitting this scenario, it can lead to issues.
Encountering this issue primarily with specific model names suggests the potential for similar occurrences with other model names.
The text was updated successfully, but these errors were encountered: