-
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
Still having issues with schema, and autocomplete #3047
Comments
Hi @akilisosa 👋 thanks for raising this issue. What particular error are you getting when trying to run the |
Property 'listRoomsBySimpleCode' comes from an index signature, so it must be accessed with ['listRoomsBySimpleCode']. If i change all that, and add 'any' as the client type, i get a client error when i make the request: If you are interested in testing out the repo - this is the project i was working for the hackathon: https://github.com/akilisosa/nom-kitties-angular-v5 s I was doing it to get familiar with gen2 before i transfer my other app over. |
Hi @akilisosa thank you for the repro app. i wasn't able to see that error, i ran into some issues trying to install the dependencies:
not sure how to resolve these angular deps errors |
@chrisbonifacio those install issues might be because you have an older version of angular cli installed on your computer/cached somewhere. The updated version of nomkitties-v5 is using angular version 19 of angular which was just released a week ago, you can also just do --force to install them. and it should run. if you run into the dependency issue with appsync library:
just force that one through there are no issues. |
@akilisosa thank you! i was able to install and run the dev server. i was also able to reproduce the issue: a workaround seems to be accessing the object like this: res = (
await client.models.Room['listRoomsBySimpleCode']({ simpleCode: code })
).data; i'll mark this as a bug for the team to investigate further. |
@chrisbonifacio I'm glad you were able to get through it. While i could get past the linting error with the ['name'] syntax, when I tried to make the actual all I got an error. |
Amplify CLI Version
12.13.0
Question
I am using amplify gen2 in my angular project. I asked this question in the thursday chats, and it seemed like it resolved last time in my react app, however I cannot figure out the solution to this in my current project.
there are issues related to this, but basically what i heard in the meeting was that if its my amplify_outputs.json it should be available:
Room type:
as you can see the regular .list works. but the index ones based of the schema throw an error.
The text was updated successfully, but these errors were encountered: