Releases: lucassabreu/clockify-cli
Releases · lucassabreu/clockify-cli
v0.5.0
Changed
in
,log
andreport
now don't require you to inform a "user-id", if none is set,
than will get the user id from the token used to access the api
Added
me
command returns information about the user who owns the token used to access
the clockify's api
v0.4.0
Added
- table format will show time entry tags
Changed
- when adding fake entries with
--fill-missing-dates
, will set end time as equal
to start time, so the duration will be 0 seconds
v0.3.2
Changed
- printing duration as "h:mm:ss" instead of the Go's default format,
because is more user and sheet applications friendly.
v0.3.1
Fixed
- fixed
--no-closing
being ignored - interactive flow of
clone
was keeping previous time interval
v0.3.0
v0.2.2
Fixed
- the endpoint
workspaces/<workspace-id>/tags/<tag-id>
does not exist anymore, instead the
api.Client
will get all tags of the workspace (api.Client.GetTags
) and filter the response
to find the tag by its id.
v0.2.1
Fixed
clockify-cli report
parameter--fill-missing-dates
, was not working
v0.2.0
Added
clockify-cli report --fill-missing-dates
when this parameters is set, if there
are dates from the range informed, will be created "stub" entries to better show
that are missing entries.
v0.1.7
Added
api.Client
now supports getting one specific time entry from a workspace,
without the need to paginate through all time entries to find it (GetTimeEntry
function).
Fixed
clockify-cli report
was not getting all pages from the period, implemented
support for pagination and to get "all pages" at once intoClient.Log
and
Client.LogRange
Changed
- updated README, so it shows the
--help
output as it is now
v0.1.6
Fixed
- fixed bug after Clockify's API changed, where
user
andproject
are not
automatically provided by the "time-entries" endpoint, unless sending
an extra parameterhydrated=true
, anduser
is not provided anymore, so
now we find it using the user id from the function filter