You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 27, 2018. It is now read-only.
Hey folks! I've been asked a couple times about my plans for Harvested and supporting the V2 Harvest API.
The short of it is: Harvested will not support the V2 API.
The longer one is: Years ago, I realized how I did not enjoy maintaining API bindings. Not just Harvest, but any API bindings. I don't find the problem space that interesting compared to other software problems.
Since then, I've tried numerous times to bring on contributors to Harvested and to pass this project on so users were not left in a lurch as bug fixes and missing features were discovered. That has not been altogether that successful.
So my plans are to let Harvested die with the V1 API, whenever that ends up being removed from Harvest itself. I have not heard any sort of time frame yet, for those are are wondering, and I'm sure Harvest will be very vocal about giving users plenty of time to switch. Sounds like the timeline is already in place! https://help.getharvest.com/api-v1/
The V1 API has been deprecated but will be supported until January 1st, 2019. Please use the V2 API going forward.
Someone asked me how much effort it would be to fork Harvested and implement the V2 changes, but honestly I don't think they would gain that much efficiency over just starting anew. You are certainly welcome to do that, the codebase is MIT licensed. but I just don't see it helping that much.
To add to that, I am now considering Harvested feature frozen and I will only be fixing critical bugs. But not accepting any new feature additions. After 7 years, I'm ready to move on. But in the least disruptive way to the people depending on Harvested.
The text was updated successfully, but these errors were encountered:
@zmoazeni Hey Zach, thanks for creating harvested and sharing this!
I was wondering if anyone had attempted to add support for v2 or had started another gem for this? I'd like to use the API within my app but I wouldn't want to start building a Ruby wrapper if there is one out there already.
My searches didn't produce any results, but maybe I'm searching for the wrong keywords.
Hey folks! I've been asked a couple times about my plans for Harvested and supporting the V2 Harvest API.
The short of it is: Harvested will not support the V2 API.
The longer one is: Years ago, I realized how I did not enjoy maintaining API bindings. Not just Harvest, but any API bindings. I don't find the problem space that interesting compared to other software problems.
Since then, I've tried numerous times to bring on contributors to Harvested and to pass this project on so users were not left in a lurch as bug fixes and missing features were discovered. That has not been altogether that successful.
So my plans are to let Harvested die with the V1 API, whenever that ends up being removed from Harvest itself.
I have not heard any sort of time frame yet, for those are are wondering, and I'm sure Harvest will be very vocal about giving users plenty of time to switch.Sounds like the timeline is already in place! https://help.getharvest.com/api-v1/Someone asked me how much effort it would be to fork Harvested and implement the V2 changes, but honestly I don't think they would gain that much efficiency over just starting anew. You are certainly welcome to do that, the codebase is MIT licensed. but I just don't see it helping that much.
To add to that, I am now considering Harvested feature frozen and I will only be fixing critical bugs. But not accepting any new feature additions. After 7 years, I'm ready to move on. But in the least disruptive way to the people depending on Harvested.
The text was updated successfully, but these errors were encountered: