Repository PR List #198
No reviewers
Labels
No Label
Priority-high
Accepting-merge-requests
API
API-dependency
Backport
Blocked
Brainstorming
Breaking
Bug
Changelog
CI
Cleanup
Confirmed
Discussion
Documentation
Duplicate
Enhancement
External-dependecy
F-droid
Feature
Google-play
Improvement
Invalid
Investigate
LGTM-done
LGTM-need
Long-term
Major-release
Minor-release
Needs-cleanup
Needs-feedback
Needs-help
Priority-critical
Priority-low
Priority-medium
Question
Ready
Refactor
Regression
Release
Repository
Security
Suggestion
Support
Testing
Translation
UI/UX
Upstream
Website
WIP
No Milestone
No Assignees
2 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitnex/GitNex#198
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "8-repo-pr-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?
Will close #8
dont implement assignee anymore ...?
@ -0,0 +32,4 @@
private userObject user;
private List<labelsObject> labels;
private assigneeObject assignee;
can drop L35 ?
Yes, I will drop it.
@ -0,0 +592,4 @@
}
}
public class assigneeObject {
drop this class
See my comment
@ -0,0 +837,4 @@
return labels;
}
public assigneeObject getAssignee() {
drop this func?
See my comment
If you dont have JSON Obj "assignee" gitea API ignore this ...
-> less redundancy ...
you get the same info + more from "assignees"
related to #196
@6543 Sure, no problem. I will remove that part as it's not needed at this point.
Only thing I am worried is when creating new PR(future work) old versions of Gitea does not force assignee as mandatory. Then it will be a problem that time.
I think since 1.10.0 is out + 1.9.x support assignees and 1.8.x or below is riscy to use (securety ...) and the api stucture is not the same! (https://github.com/go-gitea/gitea/tree/release/v1.9/modules/structs) vs (https://github.com/go-gitea/gitea/tree/release/v1.8/modules/structs) we can drop this for next release I dont like to support 1.8.x and below! and 1.11.0 is on the way because a lot of refactoring has happend the next majior release is going out fast ...
@6543 I have removed assignee from model.
This PR is ready for testing.
Things to note:
Edit: There is not much difference of issue view and pr view, so will add single view for pr later in this PR.
think two things have to implemented to be usefull again:
optional
Yes, I will add single view.
I forgot about the count, thanks for the reminder.
Closed pr, will add in another pr.
Repository PR Listto [WIP] Repository PR ListAdding counter is very tricky for PRs as the repo info does not provide the counter. And PR API return paged records.
Maybe adding it to the API
/api/v1/repos/OWNER/REPO
is best?@mmarif I'll look into this (PR counter)
This PR is ready for testing.
[WIP] Repository PR Listto Repository PR Listthis need future features/improvement but I think it is ready for merge