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
I've been live testing wakapi-anyide, and I discovered some information like the editor field is lost.
According to the official hackatime docs, these are the fields, and the editor field is not used due to some wakatime incompatibility.
This means that Hackatime is pulling editor information from the user agent field, and any custom editor information is lost with the upload. Normal wakatime instances should not have this issue, but hackatime is different. This doc may be outdated, because the machine is detected correctly and here it says it isn't used. Custom editor information is still not appearing on the dashboard, though.
To solve this, we may be able to change the user agent field with custom editor information; alternatively, we can get hackatime to support the field.
The text was updated successfully, but these errors were encountered:
techy-robot
changed the title
[Bug] Multiple API fields are ignored with Hackatime, incl Editor and lines added/removed
[Bug] Multiple API fields are ignored with Hackatime, incl Editor
Nov 18, 2024
I've tried changing the user agent field with many variations, but regardless of what I do, it labels the editor "unknown," even if I specify a simple name like "test."
I've been live testing wakapi-anyide, and I discovered some information like the editor field is lost.
According to the official hackatime docs, these are the fields, and the editor field is not used due to some wakatime incompatibility.
This means that Hackatime is pulling editor information from the user agent field, and any custom editor information is lost with the upload. Normal wakatime instances should not have this issue, but hackatime is different. This doc may be outdated, because the machine is detected correctly and here it says it isn't used. Custom editor information is still not appearing on the dashboard, though.
To solve this, we may be able to change the user agent field with custom editor information; alternatively, we can get hackatime to support the field.
The text was updated successfully, but these errors were encountered: