See Employees Assigned to A Department

[rafcevallos]

Link to Ticket

Closes #7

Description of Proposed Changes

• Organized order in faker_factory.py so Seeder runs properly
• Organized urls.py: separated paths
• Moved related name from department on Employees model since that is used for function based models. We are using class-based models.
• When in the department detail view, user can now see the employees assigned to that department

Steps to Test

Outline the steps to test

git fetch --all
git checkout RC-DeptEmployees
code .

CHECKING EMPLOYEES ASSIGNED TO A DEPARTMENT

Non-Faker Users:

1. shut down the server
2. delete migrations folder
3. delete db.sqlite3 file
4. python manage.py makemigrations bang
5. python manage.py migrate
6. python manage.py runserver
7. Open DB Browser
8. Create an Employee
9. Create a Department
10. Click on the newly created department
11. You should see all the Employees assigned to that Department NOTE: Make sure the foreign keys are properly assigned

Faker Users:

1. shut down the server
2. Windows ./django_data.sh bang faker_factory or Mac django_data.sh bang faker_factory
3. python manage.py runserver
4. Click on Department
5. Click on a single Department
6. You should see the Employees assigned to that Department

Impacted Areas in Application

List general components of the application that this PR will affect:

• urls.py
• employees.py
• department_view.py
• employees_view.py
• department_detail.html
• department_list.html
• faker_factory.py

Mentions @username

@sirwin4 @hayleylandsberg @eagobert @Levi-Schubert Tag users that need to review this code

Definition of Done

1. The project must be fully documented. This includes the following:
   1. Complete README that documents the steps to install the code, how to install any dependencies, or system configuration needed.
   2. Every class must be documented with purpose, author, and methods.
   3. Every method must be documented with purpose and argument list - which itself must contain a short purpose for each argument.
2. The project must be able to run fully, and without errors, on each teammate's system.
3. Fulfills every requirement. Every line of code has been peer reviewed.
4. For projects that require unit testing, core functionality must be identified and have at least one test for each

[Levi-Schubert]

☯️

[eagobert-zz]

👍

[sirwin4]

with removal of employee reference name, :shipit: up to you how you deal with dat