-
Notifications
You must be signed in to change notification settings - Fork 79
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
TypeScript Type Inference Error with AWS Amplify Data Schema in Monorepo Environment #2564
Comments
Hi @rnrnstar2, this seems similar to an issue we are currently aware of and working on a fix for. Can you share your schema to reproduce locally so we can confirm? |
this is data resource.ts. |
@rnrnstar2 can you check your tsconfig and confirm that you have strict mode enabled? If it's enabled and you are still experiencing this issue, please let us know. |
created a repo with this issue - still a blocker for me |
@waynet-ihm thank you! I was able to reproduce your error right away. Although now I realize it's different from the one originally described here. Perhaps this deserves its own issue. If you create a new issue, I'll mark it a bug for the team to investigate further. |
Hi @rnrnstar2 , just wanted to share an update on this: the team is aware of and working on a fix for these reference/type annotation errors |
Hi @chrisbonifacio or @stocaaro any update on when this will be resolved? I am facing similar issue described here. |
@neerajvisal - the issue should be resolved now. Please run @waynet-ihm - I was able to successfully run
|
I have confirmed that updating to the latest version of |
This issue is now closed. Comments on closed issues are hard for our team to see. |
Environment information
Description
I'm encountering a TypeScript type inference error when using AWS Amplify's data schema in a monorepo environment. The node_modules directory is present only at the root level of the monorepo.
Steps to Reproduce:
Expected Behavior:
The type inference should correctly recognize the string type for the
name
property without any errors.Current Behavior:
TypeScript throws an error, indicating that the string type is not assignable to the expected type, which includes various methods and properties.
Environment:
Turborepo
The text was updated successfully, but these errors were encountered: