Editing the name from the settings does not update in the database.

[omarNaifer12]

[omarNaifer12]

Hi, if no one is working on this issue, I can start with it.

[omarNaifer12]

/attempt

[github-actions]

Assigned the issue to @omarNaifer12!

[rajdip-b]

Thanks! @omarNaifer12

[rajdip-b]

I saw your PR, and it felt a bit off to me. You see, the API has been tested in and out, but the platform might have errors. I just noticed in the issue video that you got an error when you tried to update your profile. Can you zoom in on that error a bit?

[omarNaifer12]

The error occurs because the backend sends a conflict response, as shown in the shared image. The error message indicates that the email already exists. This happens because the updateSelf function in the backend throws a ConflictException if userExists is true:
throw new ConflictException('User with this email already exists');

I believe this issue arises because the same email as the user's current email is being sent. To fix this, I added an extra condition to prevent this scenario, and it worked for me.

If you encounter any errors with my changes, please share the error message and status code so we can determine if it’s a different issue that I haven’t faced.

[rajdip-b]

This is more of a frontend issue. The frontend shouldn't be sending the email in the body if a new email isn't specified. So perhaps you can fix the malformed request body. That will fix this issue.

[rajdip-b]

🎉 This issue has been resolved in version 2.9.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀