iP:
Level-7, Level-8A-MoreOOP, A-Packages, A-Gradle, A-JUnit, A-JarA-JavaDoc, A-CodingStandard, Level-9tP:
Reminder about the deadline for the weekly project tasks:
master branch of your fork to the master branch of the upstream repo (https://github.com/nus-cs2103-AY2223S1/ip)[{Your full/partial name or your Github username}] iP[Richard Mathews Chee] iP or [Rich ... hee] iP or [TheRichMat] iPThe PR will update automatically to reflect your latest code every time you push code to your fork. As a result, it provides a convenient way for us to access the current state of all your iP code from one location.
Level-7, Level-8branch-Level-7. Without merging that branch, go back to the master branch and implement the other increment in a separate branch named similar to the first (i.e., branch-{increment ID}). Now, go back to the master branch and merge the two branches one after the other. As before, tag the commit (in the master branch, after merging) that achieves the respective deliverable, and push to your fork.b1 to the master branch, you need to push both the master and the b1 branches to the fork. Pushing the master branch does not automatically take the b1 branch along with it just because it is already merged to the master branch.A-MoreOOP, A-Packages, A-Gradle, A-JUnit, A-JarWhy more OOP?
One of the increments below asks you to push the design more towards the OOP approach. This is a good point to remind you that OOP is not a silver bullet or always the right choice. While it is the most widely used and possibly the right choice for a variety of situations, it may not work well for other situations, and it has plenty of detractors and known problems.
OOP has been chosen as the primary paradigm for this module and you are expected to try to push it to its limits. That should give you a first-hand experience of OOP's strengths and weaknesses. Furthermore, OOP (or any other paradigm) will appear worse than it really is if not used correctly, and learning to use it correctly in increasingly larger systems is another objective you can aim for in this module. As you do the tP later, you'll also realize that while OOP is used for the internal design of its components, the higher-level design is not specifically an OOP one.
We do not prohibit the use of other paradigms, however. For example, if you find a place where the functional approach is better, go ahead and use it. As you know, Java supports functional programming to a certain extent. In fact, the tP code given to you uses small snippets of functional-style code in several places.
Good OOP != OOP is good: While the module pushes you to use good OOP, do not interpret it as a message of OOP is good; it's good for some cases and not so for other cases. The best is usually a combination of approaches. Hence, you are encouraged to get better at other paradigms, the functional paradigm in particular which has been rising in popularity in some areas such as big data, AI, parallel systems.
That said, it is also preferable to use one paradigm as the primary approach and fallback on others only when the primary paradigm is clearly sub-optimal. Reason: mixing everything in equal measures might make the system even harder to understand.
master branch (no need to use separate branches).A-Gradle first, after which use the Gradle option (rather than the Intellij option) when doing A-JUnit and A-JAR as they are easier to do using Gradle.A-JavaDoc, A-CodingStandard, Level-9branch-A-JavaDoc, branch-A-CodingStandard, branch-Level-9), and then merge them one-by-one. Hopefully, you will encounter some merge conflicts so that you get to practice de-conflicting branches.A-CodingStandard) are given in this page.