Jump to content

Martien Oranje

Member
  • Content Count

    69
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Martien Oranje

  1. What version of the workflow are you on?
  2. What version of the workflow are you on?
  3. Hi! Did you install node.js? Check the install instructions if you have trouble setting everything up. Cheers
  4. I'm currently working on an update of the workflow. It is still prerelease but for anyone willing to try it out, find it here: https://github.com/moranje/alfred-workflow-todoist/releases I've been using it myself for the past few weeks and it should be fairly stable. Martien
  5. Please describe what problem you are referring to. I don't see anything out of the ordinary. Martien
  6. Whoops that's not good. I'm in the middle of a big rewrite which solves a lot of the outstanding issues l, a better updater, better notifications and better error response. I hope I'll be able to release an alpha soon. If that's not acceptable I would recommend a downgrade (find it on github). Did you ever hear anything back from Todoist? I got a note they'd look into it. But nothing definite.
  7. I've filed another bug report with this information. I'll keep you posted. Martien
  8. So it used to work then? Maybe we should file a bug report with Todoist. "Every Wednesday 9pm" used to create an auto reminder?
  9. Hi! I want to stay away from having to parse language myself. The workflow uses the REST API and uses the "due_string" property to (leave Todoist to) do it's magic. I would think it should be possible to add auto reminders this way...
  10. Hi, have you read and completed the install instructions? Are on node.js 12? An error log would help, read the instructions if you aren't sure how to do that. Martien
  11. Alfred deprecated their beta API that's the error you are getting. Update your workflow to the latest version and you should be fine.
  12. I can't be certain but sounds like you are behind some sort of firewal or proxy. Can you try another Internet connection? Martien
  13. The API key should be yours and can be retrieved from the todoist app
  14. Hi Bob, I'll try to help you but it would be most helpful if you'd be able to get me a debug log. For reference see: https://github.com/moranje/alfred-workflow-todoist#debug Also it looks like you have installed the LTS version of node.js, the latest is at v12 (that might be a problem with the workflow not working). Try to update to the latest: https://nodejs.org/dist/v12.10.0/node-v12.10.0.pkg Check back in if the above doesn't fix your problems, Martien
  15. Todoist deprecated the beta version of their api, you need the latest version of the workflow (5.8.3). Be sure to upgrade your node.js version as well (at least 11.5). Cheers
  16. I haven't updated myself, but I would think the workflow should be backwards compatible, since I'm not seeing anything about workflow incompatibility in the release notes.
  17. Today (en) and heute (de) I understand (seemingly) doing nothing because that's the default option. But tomorrow (en) or morgen (de) should definitely do something (and those are working on my end). Just bear with me here, while I make sure I understand fully. So if I understand right creating a task with `todo test, morgen` with the locale set to german will create a task but today (rather than the expected tomorrow) right? Martien
  18. Does what it's supposed to (from what I can see at the logs and what I have tested on my machine). I think we may have ourselves a bit of miscommunication. What did you expect the app to show? Does it work with 'Tomorrow'? For allowed date formats, check out: https://github.com/moranje/alfred-workflow-todoist#usage
  19. https://github.com/moranje/alfred-workflow-todoist#debug
  20. Do you have an error log by any chance? (See my last comment)
  21. Do you have the language set to German? Check out the docs to see how that would work. If that doesn't work see if you can find an error log for me.
  22. The problem is the comma. Anything after the comma is expected to be the date so it needs to be the last thing you specify. The reason for this is that multilanguage date string parsing is hard, and Todoist has already solved this problem. But in order to have Todoist read the date I need to to send it a string that holds just the date (string). I do this by having the date string between a comma and the end of the string. This used to be better documented but I guess I took that out with the last rewrite. Hope that helps, Martien
  23. For what it worth: the workflow needs some time to parse the text and load the cache from disk needed to populate the projects and labels. You can type as fast as yo u like, but you may need to wait a fraction of a second before you hit ENTER after the last keystroke.
×
×
  • Create New...