Remember your boss in ToyCity Part 1? Well, they loved your sales report so much, they decided to surprise you with an extra special request.

Your boss was also wondering if you could somehow package the code, so they can reuse pieces of it in future sales reports.

In this lesson, you are going use the new skills you've learned to refactor your ToyCity code from Part 1. You will restructure your code using methods, and output your reports to a file instead of the command line.

You will also start using Git to track the changes you make to your project files.

You should have completed all the necessary steps for finishing this project in ToyCity Report Generator, Part 2. Before submitting, ensure your program does the following:

• Outputs all the same data as ToyCity Part 1.
• Outputs the properly formatted report to a report.txt file.
• Uses methods to reduce code duplication and increase readability.
• Is accompanied by a log.txt file containing your Git logs documenting your commit history (containing at least three meaningful commits).

Remember, you should not modify any of the existing code we have provided for you.

Before submitting your project for evaluation, we recommend that you check that each of the following is true:

• Your program runs without any errors
• You are proud of your project and its output
• You completed your project according to the instructions
• You checked your project against the rubric
• Create a zip file with your For instructions on how to do this, click here. When you feel ready to submit, use the blue 'Submit Project' button below!