The documentation specifies that the GET request to /users/{username}/activity/current always specifies that the started field is in UTC time (by including the Z at the end):
{
"started": "YYYY-MM-DDTHH:MM:SS.ssssssZ",
"duration": "10",
"heartbeat": {
"language": "c",
"hostname": "hostname1",
"editor_name": "Neovim",
"project_name": "cool_project22"
}
}
However, in reality that "Z" is not included. Here is an example response that I got:
{
"started": "2023-12-17T12:03:20.938417739",
"duration": 240,
"heartbeat": {
"project_name": "testaustime-frontend",
"language": "typescript",
"editor_name": "vscode",
"hostname": "ideapad"
}
}
I believe the same problem exists for all other timestamps that are returned from any endpoint. We already have an issue in the frontend for this, but I think it would be best to fix in the backend.
Also, it seems that the duration field is a number instead of a string.
The documentation specifies that the GET request to
/users/{username}/activity/currentalways specifies that thestartedfield is in UTC time (by including theZat the end):{ "started": "YYYY-MM-DDTHH:MM:SS.ssssssZ", "duration": "10", "heartbeat": { "language": "c", "hostname": "hostname1", "editor_name": "Neovim", "project_name": "cool_project22" } }However, in reality that "Z" is not included. Here is an example response that I got:
{ "started": "2023-12-17T12:03:20.938417739", "duration": 240, "heartbeat": { "project_name": "testaustime-frontend", "language": "typescript", "editor_name": "vscode", "hostname": "ideapad" } }I believe the same problem exists for all other timestamps that are returned from any endpoint. We already have an issue in the frontend for this, but I think it would be best to fix in the backend.
Also, it seems that the
durationfield is a number instead of a string.