#162575779 Fix Bug in Profiles App

[ghost]

What does this PR do?

This PR adds functionality for auto-populating the username filed on the Profile model when a user signs up.

Description of Task to be completed?

How should this be manually tested?

It can be tested on Postman as below:

1. Run the following commands in Terminal

git clone git@github.com:andela/ah-jumanji.git
git checkout fix-bug-in-profiles-app-162575779
virtualenv venv && source venv/bin/activate
pip install -r requirements.txt
touch .env

Update the .env file as follows:

DATABASE_URL=postgres://{postgres-db-username}:{postgres-db-password}@localhost/ah_jumanji
export PROTOCOL="http://"
export EMAIL_HOST_USER="jumanjidevs32@gmail.com"
export EMAIL_HOST_PASSWORD="jumanji@32"

Continue in Terminal

python manage.py makemigrations && python manage.py migrate
python manage.py makemigrations profiles && python manage.py migrate profiles
python manage.py runserver

2. Send a POST {your-server-root}:8000/api/users/register request with a payload similar to:

{"user": {
   "username": "cmithamo",
   "email": "cmithamo@mymail.com",
   "password": "Strong#3-password"
   }
}

to register a User and generate an auth token
3. Activate the account by clicking on the link sent in the activation email.
4. With the auth token generated, send a GET {your-server-root}:8000/api/users/profiles request to view the auto-generated profile for the user just now created.
[See screenshot for sample response]

6. Run the tests using pytest with the command pytest [or pytest -v for verbose output].

Any background context you want to provide?

Previously, on user account creation, the first_name field on the Profile was populated with the username of the registered user. This PR changes that, because there is functionality which depends on querying the profiles table by username.

What are the relevant pivotal tracker stories?

#162575779

Screenshots (if appropriate)

View on GET /api/users/profiles with logged in user

Questions:

Checklist:

• My code follows the style guidelines of this project
• At least 2 people have reviewed my PR
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• My PR has one commit.

[GransonO]

That's a good step to resolving the bug. Can be merged so that other users can implement the recent changes.

[GransonO]

Though I noticed the Coverage has decreased? why would this be so?

[mashafrancis]

Good step in resolving the error in the code.