linustws / ped

hey there 👋

👩‍💻 About Me

👋 Hi, I'm a Year 3 NUS Com Science undergrad passionate about leveraging tech to drive innovation and solve real-world problems. As someone who likes to be efficient, I'm currently exploring ways to streamline workflows, automate processes, and enhance overall system efficiency, as I hone my skills in DevOps.

I'm eager to connect with like-minded professionals, collaborate on exciting projects, and share insights. Feel free to reach out! :)

- 🔭 I’m working as a full-time student
- 📚 I'm currently taking CS4261, CS3230, CS2106, CS2105 and ACC1701X
- ⚡ In my free time I like to dance, game and create stuff

🛠 Language and tools

ped's Issues

Example code given under add command does not work

Their UG gave this example code for the add command: add n/booked tennis court /2023-02-01 /2023-02-02

but it gave me an error when i copied it and entered it.

Recur command does not recur every day if i enter a recur by month followed by recur by day

added event -> recurred that event by month -> recurred that event by day. the recurred by month works but the recurred by day only works for 1 month, not until the specified date. ie i recurred the event that is added on 2023-03-31 but it only recurred for all the days in april, not until 2024-01-01 that i specified.

It seems like there are errors thrown here:

Adding of events that overlaps in time is actually possible

Their UG states under the add command that "Adding of events that overlaps in time is not allowed."

But they did not enforce this. I managed to add events that are overlapping in time, as shown by the "dance" event that i added below. Whether completed or not this is currently possible.

Recurring of events inaccurate for edge days

I added an event on day 31, then using the example code they provided: recur 1 d/2024-01-01 every/MONTH, i tried to recur this event every month. The thing is, it added an event on day 30 for each month, not day 31.

Then i tried to recreate this error by extending the example code to : recur 1 d/2026-01-01 every/MONTH

Apparently, the date on which the event is added is capped by the days that the month has. i.e. if feb has 29 days and i tried to recur an event on day 31, it would add the event on day 29 for feb, and for the subsequent months, until it it capped again by like let's say the next year when feb has only 28 years, as shown below

Personally, I think if the month does not has the day of the recurred event, it should not be added to that month, i.e. like feb does not have day 31, so my event should not be added in feb, to make it consistent.

List and calendar dont match

i recurred both the dance and sleep events but in the calendar it shows 2 of dance events on each day, when it supposed to show 1 dance and 1 sleep event on each day.

Might crash program or hang for cases like recur 1 d/2050-01-01 every/DAY

Programs just hangs, need to force quit. Should probably inform users in the UG to not recur events every day/for a long period of time.

Undo command does not work for this sequence: (add -> recur by month -> recur by day -> undo)

regarding the previous issue, i followed it up with an undo command, but nothing happened.

looking at my console it seems like errors were thrown not sure whether this is part of undo command or this is part of the recur by month then recur by day:

End time can be before start time

Their UG states under the add command that "Start time should come before end time."
but this is not enforced in the product. I managed to add events that have end times before their start times. E.g. the running event that I added