joeriharleman
commented
2 years ago Hello @tini5000!
Thank you for submitting your issue. Unfortunately this repository is largely unmaintained, which means issues remain unseen and do not get dealt with in a respectable manner. We're sorry for not getting back to you sooner.
This issue has been around for a long time so we will close it for now, but please let our excellent 24/5 support staff know you if you have any unresolved issues with our platform, documentation or APIs. They're also really good at noting down feature requests for our development teams. Please find them on our support page by clicking the little icon in the bottom right corner of the screen.
Kind regards, Joeri from Toggl
There are a number of cases when the server responds with a 200 OK status code and a "null" in the response body. I'm giving here an example of Workspace Tasks endpoint: Raw Request (monitored in Fiddler) : GET https://api.track.toggl.com/api/v8/workspaces/3340127/tasks HTTP/1.1 Host: api.track.toggl.com Authorization: Basic NmFjZjcwZmMwZTRhYWNiMDg1YjE0NDk1MWUyOGMwMzk6YXBpX3Rva2Vu Accept-Encoding: gzip, deflate User-Agent: CData Data Provider Engine - www.cdata.com - Accepts: gzip
Raw Server response: HTTP/1.1 200 OK Server: nginx Date: Wed, 24 Nov 2021 11:16:17 GMT Content-Type: application/json; charset=utf-8 Content-Length: 4 Cache-Control: no-cache, private, no-store, must-revalidate, max-stale=0, post-check=0, pre-check=0 X-Toggl-Request-Id: b949a356e337ffb3ebe219bd3224bf2e X-Service-Level: GREEN Via: 1.1 google Alt-Svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
null
Could this response be fixed by returning an empty array [ ] , instead of a null, in cases when there is no records (no tasks for the given workspace in the above example)?