Jump to content

Martien Oranje

Member
  • Content Count

    45
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Martien Oranje

  1. 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.
  2. You may be right about the case-insensitivity, I think in this case-sensitivity may be preferred. That's a piece of documentation that stems from a time when the workflow didn't recommend projects yet. Not sure I understand the second part. Can you show me the debug output?
  3. Just to make sure: did you have a project called Collateral when submitting the above query? If it's not already there it won't be created.
  4. I added more useful error messages to the latest patch release. It should give you a helpful error if node.js isn't installed as well as when the API token is missing. Download
  5. Add you api key as explained in the docs: todo:setting token {api token} Example: todo:setting token 2d2e2a334c5f36e7a7c43b46e
  6. Great, thanks for the feedback! Martien
  7. Yes I could do that, but I fear that some control characters like `,` and `:` and `;` might be problematic. I've opted for the long way. I've spun up a beta version for @Pavel A to test. My Cyrillic literacy is not very good but seems to work. If you can confirm it works I'll merge the changes to master. https://drive.google.com/file/d/1nmdTrYqpt7Ef1Dzt1k9PAA1oVPSMiwAh/view?usp=sharing
  8. Those aren't matched by the parser either!
  9. Right now the parser only supports latin characters. I hadn't considered other scripts. Is there a non-capital and capital range that includes all characters (like `a-z` and `A-Z`)? Edit: that would seem to be `а-я` and `А-Я` am I right? Edit 2: or perhaps [Ѐ-Ӿ] (as recommended here)
  10. Hi ystian, How can I help you?
  11. Yeah, the use of spread operators in objects was included in node.js in version `8.3`
  12. The right way is without brackets. 'x' should be a valid todoist token. There should be something in the first list item with some feedback about whats going on. The notification should also help with whats going on and if there's an error I expect something to show in Alfreds debug log (In alfred: Show Alfred Settings, then Tab Workflows -> select the Alfred Workflow Todoist -> in the upper right corner click the 'bug' icon -> set built-in terminal to 'Log: All information')
  13. It's been a while since I've updated this workflow, but I've rewritten it from scratch and have implemented most of the old features with extra's
  14. Maybe I misunderstood, I thought you were asking about not being able to use Todoist in German. Was that not your question?
  15. I'm afraid Todoist doesn't support German at the moment, correct me if I'm wrong. Martien
  16. I see what you are saying, I erroneously thought a high priority equaled a high number. That must have been why I never noticed. The API handles priorities in reverse order from the client. I'll throw in a conversion step. Nice catch! I must admit I have very little OSS time in January, I am using all the spare time a have for building a kitchen and baby room. The project makeover is about 85% done but still contains bugs and incomplete test suite and I rather not release a buggy version anymore :/ Martien
  17. Si you are saying you expect 1 to have the lowest priority?
  18. What is your search? I could produce an alfa build that had most of the new features implemented. But I haven't updated the test suite yet. Ps. The priorities being inverted is a could be due to the Todoist server and client reasoning different about priorities, what is your expected behaviour?
  19. Do create an issue, I'll see if I can get around to fixing the problem. Any error messages to help me along?
  20. First thought? I shouln't be allow to write code :-p. I am a little pressed for time atm so I tried to quick fix this one and should have tested it better. Also the code library needs a test suite, to protect me from myself. I'll try to fix, properly test and write and create a test suite after. Hang on.. Martien
  21. Found it, working with JSON in bash is a little tricky. Should be fixed. If not let me know. Find the updated binairy on github or use t:update (assuming you are on v3.1.5) Martien
  22. Yeah you are right, I have introduced a bug somewhere I'm afraid. I have had little free time to diagnose the exact problem I'm afraid. I'll try to fix as soon as I do. Martien
  23. Hmmm yeah, I think I do. I may have made a wrong an assumption on the characters in the API token. I made the assumption based on tokens I've seen that they are always exactly 40 characters long and only consist of numbers 0-9 and lower case letters 'a' to 'f'. Can you tell where your token is different from this (don't share the entire token)? Martien
  24. The workflow has been updated to give more visual feedback. See changelog for more information on changes. Martien
  25. Hi it's something I am willing to look in, would you mind creating an issue here on github (https://github.com/moranje/alfred-workflow-todoist/issues) so I can keep track of different requests. Also if you have any ideas on how you would like this function to work, write that down too. Also for those interested, I've just posted 3.1.4beta here which adds a better parser (namely #projects) and a little more visual feedback for the `todo add` command. Thanks Martien
×
×
  • Create New...