gitea/tea
gitea/tea
55
128
Fork 63
Code Issues 97 Pull Requests 18 Actions Releases 16 Activity

improved list output #281

Merged
6543 merged 12 commits from noerw/tea:issue-244-sorted-list into master 2020-12-09 22:04:37 +00:00
Conversation 1 Commits 12 Files Changed 11 +141 -170
noerw commented 2020-12-08 12:32:09 +00:00
Member
Copy Link

Refactors list output, enabling common functionality on all listings:

  • For now, only sorting is implemented
  • We could also could add dynamic field selection like currently in modules/print/repo.go, though that would require much more refactoring I think. Any ideas? This will be part of another PR if we really need it

fixes #244

Refactors list output, enabling common functionality on all listings: - For now, only sorting is implemented - ~~We could also could add dynamic field selection like currently in `modules/print/repo.go`, though that would require much more refactoring I think. *Any ideas?*~~ This will be part of another PR if we really need it fixes #244
noerw added 5 commits 2020-12-08 12:32:09 +00:00
0c752f5bed
move outputList into a struct 
so we can add additional functionality for all list output
All checks were successful
continuous-integration/drone/pr Build is passing
Details
f175fa03f7
sort milestones
noerw added the
kind
feature
kind
refactor
status/needs-feedback
 labels 2020-12-08 12:32:51 +00:00
noerw added 1 commit 2020-12-08 12:35:08 +00:00
All checks were successful
continuous-integration/drone/pr Build is passing
Details
b4dfb9a28f
sort milestones descending
noerw added 2 commits 2020-12-08 12:38:16 +00:00
All checks were successful
continuous-integration/drone/pr Build is passing
Details
a2ea850aa5
remove unnecessary if
6543 commented 2020-12-08 13:18:10 +00:00
Owner
Copy Link

I think we should use dynamik field selection, but only on specific lists

The issue list for example shoud have it, ... this way we can unify IssuesList, IssuesPullsList and PullsList into a single one ...

I think we should use dynamik field selection, but only on specific lists The issue list for example shoud have it, ... this way we can unify IssuesList, IssuesPullsList and PullsList into a single one ...
noerw added
status/needs-reviews
 and removed
status/needs-feedback
 labels 2020-12-08 14:49:56 +00:00
noerw added 1 commit 2020-12-08 17:49:13 +00:00
All checks were successful
continuous-integration/drone/pr Build is passing
Details
027ac7c6ea Merge branch 'master' into issue-244-sorted-list
noerw added 1 commit 2020-12-08 22:55:27 +00:00
All checks were successful
continuous-integration/drone/pr Build is passing
Details
f4bc0684dd Merge branch 'master' into issue-244-sorted-list
khmarbaise approved these changes 2020-12-09 15:58:17 +00:00
Dismissed
6543 added 1 commit 2020-12-09 21:51:28 +00:00
All checks were successful
continuous-integration/drone/pr Build is passing
Details
070a75f3e8 Merge branch 'master' into issue-244-sorted-list
6543 added 1 commit 2020-12-09 21:59:40 +00:00
All checks were successful
continuous-integration/drone/pr Build is passing
Details
a65de98854 rm empty line
6543 approved these changes 2020-12-09 22:01:47 +00:00
Dismissed
6543 removed the
status/needs-reviews
 label 2020-12-09 22:02:50 +00:00
6543 merged commit a91168fd36 into master 2020-12-09 22:04:37 +00:00
6543 referenced this issue from a commit 2020-12-09 22:04:37 +00:00
Improved list output (#281)
6543 added this to the v0.6.0 milestone 2020-12-12 10:59:08 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
kind/breaking

   
kind/bug

   
kind/build

   
kind/dependency

   
kind/deployment

   
kind/docs
  
kind
enhancement

  
kind
feature

  
kind/proposal
  
kind
question

  
kind
refactor

  
kind/security

   
kind/testing

   
kind/translation

   
priority/critical

   
priority/high

   
priority/low

   
priority/medium

   
reviewed/duplicate

   
reviewed/invalid

   
reviewed/wontfix

   
skip-changelog

   
status/blocked

   
status/has-backport

   
status/has-pull

   
status/needs-backport

   
status/needs-feedback

   
status/needs-reviews

   
status/wip

   
upstream/gitea

   
upstream/sdk
No Label
kind/breaking
kind/bug
kind/build
kind/dependency
kind/deployment
kind/docs
kind
enhancement
kind
feature
kind/proposal
kind
question
kind
refactor
kind/security
kind/testing
kind/translation
priority/critical
priority/high
priority/low
priority/medium
reviewed/duplicate
reviewed/invalid
reviewed/wontfix
skip-changelog
status/blocked
status/has-backport
status/has-pull
status/needs-backport
status/needs-feedback
status/needs-reviews
status/wip
upstream/gitea
upstream/sdk
Milestone
Clear milestone
No items
No Milestone
v0.6.0
Assignees
Clear assignees
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: gitea/tea#281
No description provided.
Delete Branch "noerw/tea:issue-244-sorted-list"

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?