use error response from backend to display correct error message

[SuyashSalampuria]

Fixes #24

[algomaster99]

I can't notice any difference on my machine. Can you send a screencast?

[SuyashSalampuria]

I can't notice any difference on my machine. Can you send a screencast?

[algomaster99]

Django has a feature to generate an object of errors like this

If you want to read how this happens, refer to Django's full_clean method. Try to check out its source code 😄

You can just get them and save it to a redux store (already happening) and render them like this:

This seems more convenient to me because:

1. We don't have to decide our own error messages on the frontend.
2. Multiple states are not needed to maintaining the string for an error message.
3. If we implement this successfully, we will automatically ensure on the back-end that we don't raise a 500: Internal Server Error.

[SuyashSalampuria]

@algomaster99 I see the control is reaching here but this line is not returned to the screen.

[nisarg73]

@SuyashSalampuria forEach always returns undefined, which is the reason you cannot see any <p> element. You can use map and this will be resolved. :)

[algomaster99]

There was some errors with your submission

I think the error is still very equivocal. No one can figure out why the error came at the first go.

Anyway, You don't need to hardcode the error message on the frontend. That's what I am saying. You can edit the backend to throw such error messages. Did you refer to full_clean? If not, please do it. I also suggest referring to omniport-frontend-faculty-profile's code to see how it's done.

[algomaster99]

@SuyashSalampuria sorry I really forgot about this
But anyway, whenever I am updating a profile, the error isn't thrown.