-
-
Notifications
You must be signed in to change notification settings - Fork 69
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
Simulating Subscriptions #23
Comments
Hi @Mudassir-23 I will try to find some time to test and see if there are issues. In any case, the problem is possibly in https://github.com/aws-amplify/amplify-cli If you have some time and want to help, you can also try to debug and try to find the source of the problem |
Historically AppSync was using MQTT not WebSocket to deliver subscriptions. Let's see if I can find some time and figure out what contribution needs to be done here. |
Hi, any planned updates in implementing subscriptions? |
@bboure Subscription with serverless-appsync-simulator work fine, its just that graphiql interface doesn't support the subscription testing yet. |
Hi @Mudassir-23 , |
It seems GraphiQL has supported subscriptions with a custom fetcher for some time now according to this blog post. |
There is an update in the amplify project According to the CHANGELOG they have fixed mocking WS. Note this changes are available in the latest version but for this we need to swicth from We tried today in our team via yarn resolutions
This looks working fine, would love to see an update on this 😉 |
Thank you @Hideman85 If you got this working, please feel free to open a PR, that would be great. Thanks |
@bboure I really appreciate your efforts in contributing to serverless-appsync-plugin and creating this awesome serverless-appsync-simulator plugin.
I'm facing problem testing subscriptions, I'm assuming subscription endpoint is ws://${IP_ADRESS}:20003/graphql
when I subscribe, a message "listening" continues to show up but on mutation, nothing would happen with a subscription(no data is received).
I'm using graphql explorer to test subscription.
The text was updated successfully, but these errors were encountered: