-
-
Notifications
You must be signed in to change notification settings - Fork 282
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
Add an error interface when the connection fails #172
Comments
Hey @blenderskool , I'm new to open-source contributions, but I'm eager to contribute to this project. I've been looking into the issue related to handling WebSocket connection failures. My plan is to implement a modal that displays clear and user-friendly error messages for different failure scenarios, enhancing the user experience. |
Hey @AyushmanSinghRajawat, please go ahead. There is already a Modal component that you can re-use for this. |
@AyushmanSinghRajawat Are you working on this? Do let me know if you need any help 🙂 |
Hey, @blenderskool sorry i was busy in a hackathon, but i am going to send a PR in a day, thank you for understanding. |
hey, @blenderskool, i am having trouble with client side (frontend) of this project. I have followed all steps in CONTRIBUTION.md but still nothing gets reflected in the ports. I think there is a step missing in CONTRIBUTION.md to open frontend as the backend is perfectly reflected in its port. Please let me know how to make it work as i am working on this issue and i am not able to test whether my solution works or not. |
@AyushmanSinghRajawat Which version of node are you using? Blaze currently works with node 16 |
I am working on version 18.18.0. How should i proceed? |
Install Node 16 using |
Thanks @blenderskool, i will get to it right away. |
Hi! I can try and take a look at this issue if no one has done it yet? |
When the connection to the Blaze server fails, no feedback is given to the user. We can show a popup with some messaging indicating this error and what can be done to resolve it.
The text was updated successfully, but these errors were encountered: