Sharing iP code quality feedback [for @karthu0301]

[nus-se-bot]

@karthu0301 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 Messages

possible problems in commit 3428cda:

Refactor commands and task handling using Java Streams

Manual loops in FindCommand, ListCommand, and AddCommand made the
code verbose and less readable. Additionally, mutable list exposure
and index-based deletion in TaskList reduced encapsulation and
flexibility.

Let's refactor the code by:
- Using Streams (`filter()`, `collect()`) to replace explicit loops
- Leveraging `IntStream.range()` for task list formatting
- Returning `Collections.unmodifiableList()` to prevent external mutation
- Using `Arrays.stream().anyMatch()` for validation checks

These changes improve readability, remove boilerplate code, and
enhance maintainability by applying functional programming principles.

• body not wrapped at 72 characters: e.g., - Returning Collections.unmodifiableList() to prevent external mutation

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.