-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
V8 API is deprecated and will be phased out soon, should change to v9 endpoints. #24
Comments
Nice catch, I'll will be taking a look at it over the weekend |
This came from an email with them about the duronly field when calling "You can indeed check for the end date being null instead of relying on the deprecated duronly field." |
Ok, so following the docs v8 endpoints will be disabled on April 1st. I've replaced the endpoints here, @LiamKarlMitchell can you give it a go? I don't have a running project that uses this module at the moment.... The docs mention some other work may be needed besides changing the endpoints, so I'm afraid it is not fully functional. |
Ok, so just coming back to this, the endpoint migration is not as straightforward as I thought, but they do have a guide, I'm implementing it here for now. Todo list before the next release:
I also found something that didn't make sense to me on their migration guide (although I don't use projects): |
I have decided to organize the modules in the same abstraction as the API reference
|
@rzfzr thanks for this library, is it possilbe that you publish the beta version with v9 on npm? |
It is published already :) |
I was searching it in the releases tab on GitHub and did not find it 🙈 |
My bad, i did not update the release tabs as I published it only for testing on my own app. |
client.summaryReport(
{ workspace_id, start_date, end_date },
(err, report) => {
if (err) {
reject(err);
} else {
resolve(report);
}
}
); |
The checklist above is updated, clients hasn't migrated completely yet, will check it out soon. Edit. I just saw that 1. reports are served from a different endpoint and 2. toggl now provides a swagger config, so I don't think I'll be implementing this soon, rather I will look into generating the rest of the client. |
The V8 API is deprecated and will be phased out soon, more info about this here https://toggl.com/blog/toggl-track-api-v9
It should be updated to V9 endpoints.
So it's probably going to break everything soon just letting you know.
The text was updated successfully, but these errors were encountered: