Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

wilsonsfh iP #640

Open
wants to merge 45 commits into
base: master
Choose a base branch
from
Open

wilsonsfh iP #640

wants to merge 45 commits into from

Conversation

wilsonsfh
Copy link

@wilsonsfh wilsonsfh commented Feb 23, 2025

Caviar

Caviar, a type of fish roe. Speak to the fish in the water for your tasks!

Do you know? Fish can drown suffocate if there is not enough oxygen in the water. (source)
Make sure to always supply oxygen into your lives as if you are a fish even among the water,

  • text-based
  • easy to learn
  • FAST to use

All you need to do is,

  1. download
  2. double-click it
  3. add your tasks
  4. let it manage tasks for you

And it is FREE!

Features:

  • Managing tasks
  • Managing deadlines (coming soon)
  • Reminders (coming soon)

damithc and others added 30 commits July 11, 2024 16:52
In build.gradle, the dependencies on distZip and/or distTar causes
the shadowJar task to generate a second JAR file for which the
mainClass.set("seedu.duke.Duke") does not take effect.
Hence, this additional JAR file cannot be run.
For this product, there is no need to generate a second JAR file
to begin with.

Let's remove this dependency from the build.gradle to prevent the
shadowJar task from generating the extra JAR file.
Merge branch-Level-8
Merge packages edit done on branch-Level-8
merge Level-7, features of Level-8, A-Packages, A-MoreOOP present
Add Checkstyle to master
wilsonsfh added 15 commits March 1, 2025 00:30
Merge Level 10 from branch-Level-10
Current situation:
The application currently sorts all tasks by date or description in a single command.

Why it needs to change:
Users need a way to view only tasks of a specific type (todo, deadline, event) in sorted order, rather than sorting all tasks together.

What is being done about it:
Introduce a 'sort \<type\> \<option\>' command that filters tasks by the chosen type and sorts them in ascending (1) or descending (2) order. Ensure the main tasks remain unchanged by sorting only the filtered subset.

Why it is done that way:
This approach allows more granular control while reusing the existing comparator logic, keeping the implementation consistent and maintaining backward compatibility.

Any other relevant info:
This feature complements the existing 'sort 1'/'sort 2' commands, so users can still sort all tasks if they prefer.
Merge C-Sort to master
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants