Return list of projects that a non-admin can track time to about harvested HOT 10 CLOSED

My initial idea for this task would be to parse the response from hitting /daily through the API. It appears that response has all a list of all available Projects to the user, along with related client info, and associated Tasks. We could catch the 404 that happens when non-admin users attempt to call client.projects.all and attempt a parse of /daily.

from harvested.

Did this thing if you want to check it out: https://github.com/efatsi/harvested/compare/non-admin-projects. My test suite is blowing up today in all random directions so I haven't written any tests around this, but it gets the job done.

from harvested.

I implemented this as well: jvdp@3cfe6f7

See: #52

from harvested.

Cool. You both have the commit bit. Feel free to run with this.

from harvested.

@jvdp big fan of what you've implemented.

from harvested.

We could merge my changes and add a clearer error message (hinting at time.trackable_projects) when requesting all projects as non-admin. This would model the Harvest API the most closely. Thoughts?

from harvested.

We could merge my changes and add a clearer error message (hinting at time.trackable_projects) when requesting all projects as non-admin. This would model the Harvest API the most closely. Thoughts?

I like this. I'm a fan of sending back a better error message and having them change their code vs detecting which resource they should hit and doing the appropriate request for them.

from harvested.

I've had to monkey patch this solution in on my project. Is this likely to see the light of day in the mainline soon? Seems like the problem has been solved already.

from harvested.

I'll have a look this week.

from harvested.

Version 1.2.0 with this functionality is now on rubygems.org.

from harvested.