Add an error interface when the connection fails

[blenderskool]

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.

[AyushmanSinghRajawat]

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.
I'm confident I can address this issue effectively. Please assign this task to me. If you have any suggestions or advice, I'm open to feedback.

[blenderskool]

Hey @AyushmanSinghRajawat, please go ahead. There is already a Modal component that you can re-use for this.

[blenderskool]

@AyushmanSinghRajawat Are you working on this? Do let me know if you need any help 🙂

[AyushmanSinghRajawat]

Hey, @blenderskool sorry i was busy in a hackathon, but i am going to send a PR in a day, thank you for understanding.

[AyushmanSinghRajawat]

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.

[blenderskool]

@AyushmanSinghRajawat Which version of node are you using? Blaze currently works with node 16

[AyushmanSinghRajawat]

I am working on version 18.18.0. How should i proceed?

[blenderskool]

Install Node 16 using nvm or n.
They allow you to install multiple node versions in the same system and manage them easily.

[AyushmanSinghRajawat]

Thanks @blenderskool, i will get to it right away.