You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to be able to surface the reminder time for todos in the Today view in Things.
so that I can connect this data with things like calendaring systems that require a timestamp.
Suggested approach
Ideally, surfacing this data would take place in its own field like the other time stamps as something like 'reminder_time' alongside the other timestamps like 'start_date'. Alternatively, the timestamp could be added to the 'start_date' field in instances where one exists. For example, as of now it shows only the date as '2024-26-24' but could show '2024-26-24 11:00:00' for an 11am reminder time.
Additional context
Near as I can tell, this data is stored in the TMTask table under the reminderTime column of the Things DB. I am having a hard time figuring out the encoding and if this is a "Things date" or something else.
Sincerest apologies in advance if I am missing something and this data is already accessible in a way I have not yet found!
The text was updated successfully, but these errors were encountered:
Goal
Suggested approach
Ideally, surfacing this data would take place in its own field like the other time stamps as something like 'reminder_time' alongside the other timestamps like 'start_date'. Alternatively, the timestamp could be added to the 'start_date' field in instances where one exists. For example, as of now it shows only the date as '2024-26-24' but could show '2024-26-24 11:00:00' for an 11am reminder time.
Additional context
Near as I can tell, this data is stored in the TMTask table under the
reminderTime
column of the Things DB. I am having a hard time figuring out the encoding and if this is a "Things date" or something else.Sincerest apologies in advance if I am missing something and this data is already accessible in a way I have not yet found!
The text was updated successfully, but these errors were encountered: