Sharing iP code quality feedback [for @oolongwater]

[soc-se-script]

@oolongwater We did an automated analysis of your code to detect potential areas to improve the code quality. We are sharing the results below, to help you improve the iP code further.

IMPORTANT: Note that the script looked for just a few easy-to-detect problems only, and at-most three example are given i.e., there can be other areas/places to improve.

Aspect: Tab Usage

No easy-to-detect issues 👍

Aspect: Naming boolean variables/methods

No easy-to-detect issues 👍

Aspect: Brace Style

No easy-to-detect issues 👍

Aspect: Package Name Style

No easy-to-detect issues 👍

Aspect: Class Name Style

No easy-to-detect issues 👍

Aspect: Dead Code

No easy-to-detect issues 👍

Aspect: Method Length

No easy-to-detect issues 👍

Aspect: Class size

No easy-to-detect issues 👍

Aspect: Header Comments

No easy-to-detect issues 👍

Aspect: Recent Git Commit Message

possible problems in commit c54c292:

docs: Add UI screenshot and update command descriptions in README

The README.md file now includes a screenshot of the UI to provide users
with a visual reference. Additionally, the command descriptions have been
updated for better clarity and accuracy.

Let's,
* add the `Ui.png` image to the `docs` directory
* update the README.md to display the image
* refine the command descriptions in the README.md

• body not wrapped at 72 characters: e.g., with a visual reference. Additionally, the command descriptions have been

possible problems in commit 0f23929:

Use Java Streams for improved code readability and efficiency

The codebase contains several areas where the use of Java Streams can
improve readability and efficiency. This includes refactoring methods to
use Streams for filtering, mapping, and collecting data.

To address these issues, the following changes have been made:

* Refactored the `getTasksOnDate` method to use Java Streams for filtering
  and collecting tasks.
* Refactored the `load` method in the `Storage` class to use Java Streams
  for reading lines from the file and creating tasks.
* Refactored the `save` method in the `Storage` class to use Java Streams
  for writing tasks to the file.

These changes help ensure the code is more concise and easier to
understand, while also leveraging the benefits of Java Streams for
processing collections.

• body not wrapped at 72 characters: e.g., * Refactored the getTasksOnDate method to use Java Streams for filtering

Suggestion: Follow the given conventions for Git commit messages for future commits (do not modify past commit messages as doing so will change the commit timestamp that we used to detect your commit timings).

Aspect: Binary files in repo

No easy-to-detect issues 👍

---

ℹ️ The bot account used to post this issue is un-manned. Do not reply to this post (as those replies will not be read). Instead, contact cs2103@comp.nus.edu.sg if you want to follow up on this post.