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

fix: deleting the date a reminder is related to should delete the reminder #2751

Open
raimund-schluessler opened this issue Jan 13, 2025 · 1 comment
Assignees
Milestone

Comments

@raimund-schluessler
Copy link
Member

          @jaylinski We should stay in accordance to the CalDAV specification, which states that relative alarms without the date the alarm is related to are not allowed. See the description in https://icalendar.org/iCalendar-RFC-5545/3-6-6-alarm-component.html:
In an alarm set to trigger on the "START" of an event or to-do,
      the "DTSTART" property MUST be present in the associated event or
      to-do.  In an alarm in a "VEVENT" calendar component set to
      trigger on the "END" of the event, either the "DTEND" property
      MUST be present, or the "DTSTART" and "DURATION" properties MUST
      both be present.  In an alarm in a "VTODO" calendar component set
      to trigger on the "END" of the to-do, either the "DUE" property
      MUST be present, or the "DTSTART" and "DURATION" properties MUST
      both be present.

So, the options 2 and 3 in your list are not possible by the specification alone. Furthermore, the user would still see the alarms being present, and might falsely assume that they are still working, where in reality they won't.

However, we are free to convert relative alarms to absolute alarms, if the related date is deleted. We could present the user with a popup to let him decide whether he wants to:

  • cancel the deletion of due or start date
  • convert relative alarms related to the deleted date to absolute alarms
  • delete the relative alarms related to the deleted date

The other option would be to not confront the user with this problem, and simply convert relative to absolute alarms. This is what we mostly do, to prevent pop-ups and dialogs as they often interfere with the workflow.

@jancborchardt and @nimishavijay might also have an opinion here.

Originally posted by @raimund-schluessler in #2743 (comment)

@raimund-schluessler raimund-schluessler added this to the 0.17.0 milestone Jan 13, 2025
@raimund-schluessler
Copy link
Member Author

Completely agreed! Relative dates make more sense anyway, and for the deletion popup I would suggest that we show it but simplify the wording to

This task has 2 alarms. Would you like to keep them?
[Keep alarms] [Discard alarms] and [Cancel]

That way the user won't be confused when the alarm that they had set with the due date in mind goes off without any warning :)

Originally posted by @nimishavijay in #2743 (comment)

@jaylinski jaylinski self-assigned this Jan 16, 2025
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

No branches or pull requests

2 participants