todoist: date function on modify wont work

Hello,

I’m using <todoist version 0.18.0> and should say thats the program is an success, just want to report a problem that I find, when I try to modify some task to set a date, this do not work, do not show some error, just do not take effect.

This is my command: tdi m -d "today" -L "Bash,Docker,Sysadmin" -p 2 6759995679

The task: 6759995679 p2 #Section @Bash,@Docker,@Sysadmin Configurar cron de zabbix alerter

Thank you, best regads.

About this issue

Original URL
State: closed
Created a year ago
Comments: 17 (6 by maintainers)

Commits related to this issue

fix(issue-#216): reworked add.go and modify.go to use due.string and updated item.go to include due struct Changed lib/item.go to send Due struct in params for adding and updating tasks. Changed add.... — committed to HacDan/todoist by HacDan a year ago
Merge pull request #225 from HacDan/issue216 fix(issue-#216): resolves modifying and setting date on task creation — committed to sachaos/todoist by kenliu a year ago

Most upvoted comments

Hello again, I would like to test the new version 1.9.0 and see the commits, it should be fixed in this version right?

I’m trying to download the file from here:

https://github.com/sachaos/todoist/releases/tag/v0.19.0

But seems like that the compiled file belong to 0.18.0 and not 0.19.0 😦

./todoist_linux_amd64 --version todoist version 0.18.0

Anyway I tested this file and the problem reported persist, thank you.

oscarenzo on Apr 18, 2023

fix merged, will be fixed in the next release.

kenliu on Apr 16, 2023

Looks like this was a change, or seems to be using a deprecated feature.

The library creates a date_string object instead of a due object in the JSON that it sends off to the API.

Currently, the internal library is sending:

{
  "args": {
    "date_string": "next monday",
    "id": "123456789",
    "labels": [
      ""
    ],
    "priority": 1
  },
  "temp_id": "redacted",
  "type": "item_update",
  "uuid": "redacted"
}

The Todoist Sync V9 APi looks for said due object, which you can still include references that the server will then interpret, like using today or next monday by creating a JSON object as such:

{
  "due": {
    "string": "next monday"
  }
}

This will require reworking the library a bit. I haven’t dug into that yet, but that’s where this needs to go next.

Reference: https://developer.todoist.com/sync/v9/#create-or-update-due-dates

HacDan on Apr 11, 2023