mentorship-backend
mentorship-backend copied to clipboard
Updating an user with empty username and name should give an error message
When updating an user with empty username and name should give an error message.
To Reproduce
Steps to reproduce the behavior:
-
Go to 'User-update user profile'.
-
Provide authorization access token.
-
{ "name": "", "username": "", "bio": "string", "location": "string", "occupation": "string", "organization": "string", "slack_username": "string", "social_media_links": "string", "skills": "string", "interests": "string", "resume_url": "string", "photo_url": "string", "need_mentoring": true, "available_to_mentor": true }
-
Click on 'Execute'.
-
Scroll down to 'Responses'.
7. current user's detail after update in" Return details of current user".
Expected behavior If the username and name are not expected to be updated to empty string and error should be shown.
Desktop (please complete the following information):
- OS: Windows 10
- Browser chrome
Hi is this bug still open. I want to work on this.
I would like to work on this issue.
@rashikaqureshi sorry for the late reply do you still want to work on this?
@isabelcosta yes.
yey! I will assign this to you then @rashikaqureshi :)
@isabelcosta @devkapilbansal I don't see any updates on the PR by the current assignee so, can I work on this?
@Aaishpra please wait for some more time for the assignee to respond. As the PR is complete and needs some minor merge conflicts only
@Aaishpra please wait for some more time for the assignee to respond. As the PR is complete and needs some minor merge conflicts only
No problem, The pr is already 5 months old that's why i asked.
@rashikaqureshi can you solve the conflicts.
I tag the assignee again. If the assignee doesn't respond within two-three days then this issue can be assigned to you
@Aaishpra please tag the team on zulip and asked for this issue. This issue will be assigned to you then. Cc:- @vj-codes
@Aaishpra hey I will be closing the linked PR due to inactivity and the issue will be available again , however it's a first timers only
issue and unfortunately you can't be assigned to this .
Do comment on any other issue you would like to work on:)
cc: @devkapilbansal
@Aaishpra hey I will be closing the linked PR due to inactivity and the issue will be available again , however it's a
first timers only
issue and unfortunately you can't be assigned to this . Do comment on any other issue you would like to work on:) cc: @devkapilbansal
Sure, No problem
I would like to work on this issue.
HI @isabelcosta , @vj-codes :wave:. I would like to take on this?
@surbhigoel191 @NenadPantelic this is a first timers only issue
and both of you have already made your first contributions so unfortunately this can't be assigned to you .
Do go through other issues and comment :)
Hi @isabelcosta @vj-codes I would like to work on this issue. Can this issue be assigned to me?
@battuAshita this issue is for *First TImers Only` and since you have already made a PR. You can't work on this issue. Go through other issues
@battuAshita this issue is for *First TImers Only` and since you have already made a PR. You can't work on this issue. Go through other issues
Ok:)
May be this issue was resolved earlier :thinking:
Removing Available
for now.
I mentioned this issue under a different issue, but I would like to be assigned this issue instead of #673 if possible!
As @devkapilbansal mentioned it might have been resolved earlier so if you could first check if this is still reproducible that would be great : ).
Hi! I did notice that the Pull Request had already gone through for this issue so I instead began working on #685 ! I created a pull request here