Level 200: Swap Codebases #6
Labels
📅 Sprint 2
Assigned during Sprint 2 of this module
🎯 Topic Code Review
Reading, understanding, and analysing code
🎯 Topic Iteration
Prototyping, testing, analysing, and refining in a cycle of development
🎯 Topic Teamwork
Working productively with other people
Level 200
For level 200, you are not allowed to work on the same codebase as you worked on for level 100.
Swap repos with a random person in your class. You do not need to coordinate your schedules.
Fork their GitHub repository to your GitHub username. You will need to give it a different name (e.g.
Project-TV-Show-Partner
), because you already have a repo namedProject-TV-Show
.Clone their repository to your laptop.
Look at their level 100 implementation.
Compare their implementation to yours. Think:
They should do the same with your repository.
Have a discussion about your answers to these questions. In class, together you should give a talk for 5 minutes about your conclusions. (Do this in small groups - we don't want to take all day).
Refactoring
Before implementing new features, take some time to change the codebase you're going to build level 200 in. Change anything you think will make it easier to add more features.
Some example ideas that you may want to think about:
Make a pull request to your partner's repo with any changes you want to make. Have them review, and when happy, merge your PR.
Adding new functionality
Level 200 is all about being able to filter episodes.
Search
Add a live search input which meets the following requirements:
When a user types a search term into the search box:
Send a pull request to your partner's repo with this functionality. Have them review, and when happy, merge your PR.
Screenshot of minimal version
Note: Provided your project meets the above requirements, it can look however you want.
Here is one example layout.
Episode selector
Add a
select
drop-down which lets the user jump quickly to a particular episode, with the following requirements:Send a pull request to your partner's repo with this functionality. Have them review, and when happy, merge your PR.
Screenshot of minimal version
Note: Provided your project meets the above requirements, it can look however you want.
Here is one example layout.
The text was updated successfully, but these errors were encountered: