Remove & Rename TrackedTimes list functions #467
No reviewers
Labels
No Label
has/backport
has/pull
in progress
invalid
kind/breaking
kind/bug
kind/build
kind/deployment
kind/docs
kind/enhancement
kind/feature
kind/lint
kind/proposal
kind/question
kind/refactor
kind/security
kind/testing
kind/translation
kind/ui
need/backport
priority/critical
priority/low
priority/maybe
priority/medium
reviewed/duplicate
reviewed/invalid
reviewed/wontfix
skip-changelog
status/blocked
status/needs-feedback
status/needs-reviews
status/wip
upstream/gitea
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/go-sdk#467
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "6543/go-sdk:rm_GetUserTrackedTimes-and-more"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
close #465
@ -0,0 +10,4 @@
<!-- tocstop -->
## Remove Functions for deprecated endpoints
Removed ... of ...
?
@ -33,0 +29,4 @@
// GetRepoTrackedTimesOptions set optional filters
type GetRepoTrackedTimesOptions struct {
User string
}
This needs
ListOptions
as well, and ideally alsosince
andbefore
(accepting RFC 3339 dates).Same for
ListTrackedTimesOptions
(they are equal I think, no need for a new type?)Remove Getusertrackedtimes() and add options to GetRepoTrackedTimes()to Remove GetUserTrackedTimes() and add options to GetRepoTrackedTimes()b217cc59a9
to6d9f68915a
2754d5ded9
tob001650be7
Remove GetUserTrackedTimes() and add options to GetRepoTrackedTimes()to Remove & Rename TrackedTimes list functions@noerw did a big refactor + add filters
@ -33,0 +31,4 @@
ListOptions
Since time.Time
Before time.Time
// User filter is only used by ListRepoTrackedTimes !!!
we shold add this filter for issues too -> Upstream TODO
created upstream issue: https://github.com/go-gitea/gitea/issues/14024
you're now passing
jsonHeader
unlike before, is this intended?most gitea api endpoints do not care if this header is set or not, but it's a good habit.
a client should indicate what "language" he speaks