feat: Edit relative reminders #3248
|
@ -70,6 +70,11 @@ export default class TaskModel extends AbstractModel<ITask> implements ITask {
|
|||
repeatAfter: number | IRepeatAfter = 0
|
||||
repeatFromCurrentDate = false
|
||||
repeatMode: IRepeatMode = TASK_REPEAT_MODES.REPEAT_MODE_DEFAULT
|
||||
/* Make sure to not return reminderDates to the server.
|
||||
The server currently supports both reminderDates (old API) and reminder (new API) and assumes the old logic
|
||||
if it still receives reminderDates.
|
||||
This line and reminderDates attributes will be removed after https://kolaente.dev/vikunja/api/pulls/1448 was merged.
|
||||
*/
|
||||
reminderDates = null
|
||||
ce72 marked this conversation as resolved
Outdated
|
||||
reminders: ITaskReminder[] = []
|
||||
parentTaskId: ITask['id'] = 0
|
||||
|
|
Reference in New Issue
If
reminderDates
isnull
why do we still define it?We want to make sure to not return reminderDates to the server. The api currently supports both reminderDates (old API) and reminder (new API). If the frontend still sends the old reminderDates array back to the server, it assumes the old logic and ignores the new reminders. The whole thing will be removed, if the reminderDates will be entirely removed from the server.
Can you add this as comment to this line?
ok