Turner Houghton

I am also getting this error. EDIT: After some more testing it appears that this is only an issue when attempting to retrieve datasets that were created in the AWS...

I believe this is also related to https://github.com/aws/amazon-cognito-js/issues/51 As I said in the other thread, I think this is an issue with the AWS console possibly, and not `amazon-cognito-js`. Manually...

I also have this issue EDIT: I think it may be an issue with the publisher, because it worked fine when I used the normal AWSMqtt.connect() function. Also make sure...

Nearly 4 years later and AppSync still doesn't forward default arguments and inputs to resolvers, is there some unexpected complexity to implementing this or has it just not been prioritized?

posting in case anyone else stumbles on this, adding this mock to my test files fixes the issue but to other people's points it would be nice if this followed...

Last I checked the team responsible for maintaining the amplify-appsync-simulator does not consider testing outside of Amplify to be a supported use case, see their response in this issue: https://github.com/aws-amplify/amplify-category-api/issues/692...

Has there been any movement on this? I would very much support a more intuitive way to split up CDK apps across different projects, as of now the CDK assumes...

Sorry, I didn't see this issue. What you will want to do is install everything, then run `npm run build`, and upload `dist` folder to s3.