Feat: Displaying Error Message from Backend in Toast Notification

[Saksham2k3s]

Describe the feature

Currently, the application makes an API call using Axios to create an account. On a successful response, a success toast message is shown, and the user is navigated to the home page. However, when an error occurs, a hard-coded error message (Failed To create account) is displayed in every case. I want to display the error message received from the backend in the toast notification instead of the hard-coded message.

Add ScreenShots

Record

• I agree to follow this project's Code of Conduct
• I'm a GSSOC'24 contributor
• I want to work on this issue

[Saksham2k3s]

@VanshKing30 Please assign this issue to me under GSSOC'24

[Abhinav-Sharma06]

@VanshKing30 @Saksham2k3s please assign me this task under GSSOC 2024. I am confident that I can fix this task

[hustlerZzZ]

This will expose major backend errors. You have to check if any unsuccessful call doesn't leak any type of backend data!
@Saksham2k3s

[Taranpreet10451]

Can you please assign this to me.

[hustlerZzZ]

Can you please assign this to me.

How are you going to proceed?

[Taranpreet10451]

I will use a toast notification library like "react-toastify" or any other you are using to display the error message.

[hustlerZzZ]

I will use a toast notification library like "react-toastify" or any other you are using to display the error message.

This will expose major backend errors. You have to check if any unsuccessful call doesn't leak any type of backend data!

[Taranpreet10451]

1.We handle different types of HTTP error status codes separately.
2.For common errors like bad requests, unauthorized access, and resource not found, we provide generic error messages to the client without exposing detailed backend information.
3. For other types of errors where there's no response from the server or if there's an unexpected error, we provide a generic error message as well.

[hustlerZzZ]

1.We handle different types of HTTP error status codes separately. 2.For common errors like bad requests, unauthorized access, and resource not found, we provide generic error messages to the client without exposing detailed backend information. 3. For other types of errors where there's no response from the server or if there's an unexpected error, we provide a generic error message as well.

Give time to @Saksham2k3s . If he wont then I will assign this to you

[github-actions]

Hello @Saksham2k3s! Your issue #182 has been closed. Thank you for your contribution!