Mentorship-backend: Error message for entering less than 4 characters for username under update user profile.

Created on 18 May 2020  ยท  10Comments  ยท  Source: anitab-org/mentorship-backend

When we enter username less than 4 character, the error message should be listed under Responses.

To Reproduce

Steps to reproduce the behavior:

  1. Go to 'user-update user profile'
  2. provide authorization access token
  3. {
    "name": "123โ€,
    "username": "123",
    "bio": "string",
    "occupation": "string",
    "organization": "string",
    "slack_username": "string",
    "social_media_links": "string",
    "skills": "string",
    "interests": "string",
    "resume_url": "string",
    "photo_url": "string",
    "need_mentoring": false,
    "available_to_mentor": false,
    "location": "string"
    }

  4. Click on 'Execute'

  5. Scroll down to 'Responses'

  6. Screenshot (81)

Expected behavior
That error message should be listed in the responses.

Desktop (please complete the following information):

  • OS: Windows10
  • Browser chrome
Coding

Most helpful comment

@devkapilbansal thank you got it:)

All 10 comments

@faznan3nazer Can I work on this issue?

Hi @faznan3nazer ,
Can you assigned this to me? I have no current issue in progress.
Thanks

Hey can you please assign this issue to me

Assigning you @priyanshuone6
Happy coding!

@vj-codes @isabelcosta this issue is already resolved in #959 when testing and fixing APIs as per this comment https://github.com/anitab-org/mentorship-backend/pull/959#issuecomment-756008533. Kindly close this issue and linked pull request.

@devkapilbansal I still don't see a response under 400 responses in update user profile,can you please elaborate ?

959 is for register endpoint , this is for update user endpoint.

Closing this as it was a duplicate of #574

CC: @isabelcosta

@devkapilbansal I still don't see a response under 400 responses in update user profile,can you please elaborate ?

959 is for register endpoint , this is for update user endpoint.

@vj-codes it was solve in another issue but I mentioned #959 because there the message was corrected by @NenadPantelic stating USERNAME_HAS_INVALID_LENGTH rather than USERNAME_FIELD_IS_EMPTY

@devkapilbansal thank you got it:)

Was this page helpful?
0 / 5 - 0 ratings