The iP (and the tP) undergoes changes after each semester. As such, teething issues are a possibility. If you encounter any problem while doing the iP/tP, please post in the forum so that we can take necessary actions.
We discourage you from doing project tasks allocated to future weeks. Reasons: In order to help you gain (and also to better simulate real projects), we want the project work to be and span a longer period, rather than to be done as a short burst.
Reminder: as per iP grading criteria, some increments need to to be done in each week for you to get full marks.
Please follow instructions carefully. Any deviations can cause our grading scripts to miss your work (and result in you not getting credit for the work).
Note the typical deadline weekly project tasks:
But as there are no tutorials this week, you have until the next lecture to finish this week's iP tasks.
- Read the following two sections, if you haven't done so already:
- Ensure you have followed the sections of the following module tools:
Read through this week's topics before starting the project.
If you encounter technical problems while doing the iP, follow the guidelines given below:
- Fork https://github.com/nus-cs2103-AY2223S2/ip, while noting the points below:Keep the fork name as
ipor else our grading scripts will not be able to detect it. You can change the fork name to something else after the semester (and the grading) is over e.g., after receiving your grade for the module.Untick the
[ ] Copy the master branch onlyoption so that you get a copy of the full repo.
- Enable the issue tracker of your fork (Go to
Settingsof your fork, scroll to the
Featuressection, and tick the
Issuescheckbox). Reason: at times we post feedback on your issue tracker.If the issue tracker is enabled, you should be able to visit the following URL
- Clone the fork onto your computer.
- Set up the project in your IDE as explained in the README file, unless you don't wish to use an IDE for the project.
4 Add Increments while committing frequently:
A-Enums Thu, Jan 19th 2359
Implement the given below in the given order.
- From this point onward, commit code at important points. Minimally, commit after completing each increment.
Remember not to commit
.classfiles and any other file that should not be revision controlled.
From this point onward, after completing each increment,
git tagthe commit with the exact increment ID e.g.,
git pushthe code to your fork
Remember to take note of our plagiarism policies, if you haven't done so already:
Q. How are the iP git tags used in grading?
Q. What if I discovered a bug after I finished an increment?
Q. I did multiple increments in the same commit. How to fix?
Q. The requirements of an increment scheduled for this week is already satisfied by the work I did in an earlier week. What now?
Q. My iP increments are not detected by the dashboard because I forgot to push my tags earlier. What now?
Q. Oh no! I made a mistake in my tag/branch name.
Level-1: Greet, Echo, Exit
Level-2: Add, List
Level-3: Mark as Done
Level-4: ToDo, Event, Deadline
A-TextUiTesting: Automated Text UI Testing
Level-5: Handle Errors
A-Enums: Use Enums if-applicable