Currently we ping the servers on object creation to see if our session is still fresh. Ideally we could skip this, and try to do a login the first time we call a method that gets back an authorisation error.

This would double the speed of most of the command line scripts.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Similar to -y, but allow specifying a date (OK if it has to be ISO-8601 format).

Would be nice if the date switch also worked for -l.

Today I wanted to check what I had done "last Friday." So then I was like, oh wait, what was last Friday's date? Umm...oh, March 8. You know, why can't I just use -d "last Friday"? pfenwick is smart. I bet he can add this in like 10 minutes. Let us open a self-referencing GitHub issue.

It would be awesome if logins were cached, so the idone command-line tool wouldn't need to relogin every time.

To reproduce: idone --help

It actually shows a bit of help (but not the canonical help like -h), but then falls through to -c.

Apparently one can login using an email address instead of a username. Our code is not expecting this. Either:

1. Detect attempts to login by email address and die noisily (asking for username).
2. Fix the code to be email address friendly.

I use iDoneThis to keep track of what I did last on the various projects I juggle. Sometimes I last juggled particular projects on days before yesterday and don't remember exactly which. I'd love a way to enter a range of dates and just see all the dones dumped from that timeframe. In fact, when I think about it now, what I'd love is this date-range functionality because then I could just grep after what I'm looking for. If I need better search, I can open a web browser and do it on iDoneThis. But normally I don't need really good search, just something to grep.

It'd be a plus if when in date-range mode every task could be prefixed with the datestamp.

Theoretical invocation and output:

`idone -r -s "four days ago" -e "today"

2013-03-18: Did some awesome stuff.
....
2013-03-22: Posted new issue to pfenwick/idonethis-perl.`

There is probably a neater way to format the command. Maybe just -r "four days ago,today". But I think the underlying meaning of my request is conveyed :)

So often when I type idone -y or idone -d, I actually just want to list out tasks from a previous day. Naturally, this puts me into input mode automatically, since that is the default behavior.

Is it possible to set default action per item? Mind that I do want to go into entry mode with just idone, but when specifying a date switch it'd be nice to list by default unless I explicitly specified -c.

It would be extra-cool if it could detect if I entered a string at the end of my incantation containing -d or -y and sent a single entry to iDoneThis instead of listing. However, that deviance in behavior might not be intuitive, so it's just a hope.

(From a convo with Tony)

Teams I've never used, are they a paid feature? If you're on a team, do you also have a personal calendar?

Both this and GH #11 are actually intertwined somewhat. From memory, we need the username to figure out how to path to our API endpoint. However, if we assume that we get redirected to /cal/ on a successful login, then we can use that to figure out where our end-point should be. It just needs to be cached, and we already have a cache directory for things like that. :)

Currently the code always wants a cache, and it always wants it in the XDG approved location. If that can't be created (because a parent directory doesn't exist), then we die on object creation:

Can't mkdir('/home/pjf/.cache/webservice-idonethis-perl'): No such file or directory at /home/pjf/perl5/lib/perl5/WebService/Idonethis.pm line 55

Currently the only workaround for this is to make the directory the WS::Idonethis is expecting (eg: mkdir ~/.cache), however it would be nice to allow for cacheless running (which will always require a login) or for the cache directory to be specified elsewhere (possibly via an object, so we can use things like CHI).

v0.10 produces warnings when printing unicode, and then prints it correctly anyway.

Dev (which will be v0.11) doesn't produce warnings.

No testing has been done for unicode input (either via stdin or @argv).

utf8::all may be our best solution here, although it would add a few dependencies.

In my brain, -y is yesterday, and -yy is the day before yesterday. This would be super handy.

Getopt::Long with the +v specifier seems to be the way to go here.

Would be great to be able to just do idone -r -7d and have it mean idone -r '-7d,0d'. Tasks within the last week.

For extra extra credit, make that the default behavior of the -r switch.

In summary, range-querying goes from one to three modes of behavior:

Two arguments: Same as now.
One argument: Assume range is between first -r argument and now.
Zero arguments: Assume range is between one week ago and now.

This would open up new possibilities for integrating the Perl app into other tools that shelled out. e.g. a web app. (There'd obviously be other issues with giving people your iDoneThis password, but I'm thinking broadly here.)

(Original request was also to include command-line switches, this is now implemented as the -f switch)

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.