Repository PR List #198

Merged
mmarif merged 7 commits from 8-repo-pr-list into master 2019-11-24 12:43:01 +00:00
Owner

Will close #8

  • PR list
  • Single pr view
  • DIff view
Will close #8 - [x] PR list - [x] Single pr view - [x] DIff view
mmarif added this to the 2.3.0 milestone 2019-11-15 10:08:59 +00:00
mmarif added the
Feature
label 2019-11-15 10:08:59 +00:00
mmarif self-assigned this 2019-11-15 10:09:00 +00:00
6543 reviewed 2019-11-15 13:29:12 +00:00
Dismissed
6543 left a comment
Member

dont implement assignee anymore ...?

dont implement assignee anymore ...?
@ -0,0 +32,4 @@
private userObject user;
private List<labelsObject> labels;
private assigneeObject assignee;

can drop L35 ?

can drop L35 ?
Author
Owner

Yes, I will drop it.

Yes, I will drop it.
@ -0,0 +592,4 @@
}
}
public class assigneeObject {

drop this class

drop this class
Author
Owner

See my comment

See my comment
@ -0,0 +837,4 @@
return labels;
}
public assigneeObject getAssignee() {

drop this func?

drop this func?
Author
Owner

See my comment

See my comment
Member

If you dont have JSON Obj "assignee" gitea API ignore this ...
-> less redundancy ...
you get the same info + more from "assignees"

related to #196

If you dont have JSON Obj "assignee" gitea API ignore this ... -> less redundancy ... you get the same info + more from "assignees" related to https://gitea.com/gitnex/GitNex/issues/196
Author
Owner

@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.

@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.
Member

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 ...

I think since 1.10.0 is out + 1.9.x support assignee**s** 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 ...
Author
Owner

@6543 I have removed assignee from model.

This PR is ready for testing.

Things to note:

  • Single PR comments view is not part of this PR. Only list of PRs.

Edit: There is not much difference of issue view and pr view, so will add single view for pr later in this PR.

@6543 I have removed assignee from model. This PR is ready for testing. Things to note: - Single PR comments view is not part of this PR. Only list of PRs. Edit: There is not much difference of issue view and pr view, so will add single view for pr later in this PR.
mmarif added the
LGTM-need
label 2019-11-15 16:57:06 +00:00
Member

think two things have to implemented to be usefull again:

  • PR single view
  • PR count on the top of the tab (like at issues)

optional

  • unified way to display closed issues/PR
    • closed issues have it's own tab
    • closed PR are not visible anymore
think two things have to implemented to be usefull again: * [ ] PR single view * [ ] PR count on the top of the tab (like at issues) optional * [ ] unified way to display closed issues/PR - closed issues have it's own tab - closed PR are not visible anymore
Author
Owner

Yes, I will add single view.

I forgot about the count, thanks for the reminder.

Closed pr, will add in another pr.

Yes, I will add single view. I forgot about the count, thanks for the reminder. Closed pr, will add in another pr.
mmarif changed title from Repository PR List to [WIP] Repository PR List 2019-11-16 08:27:49 +00:00
mmarif removed the
LGTM-need
label 2019-11-16 08:27:58 +00:00
Author
Owner

Adding 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?

"open_pr_counter" : 2
Adding 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? ``` "open_pr_counter" : 2 ```
Member

@mmarif I'll look into this (PR counter)

@mmarif I'll look into this (PR counter)
mmarif added the
LGTM-need
label 2019-11-17 20:21:02 +00:00
Author
Owner

This PR is ready for testing.

This PR is ready for testing.
mmarif changed title from [WIP] Repository PR List to Repository PR List 2019-11-17 20:23:01 +00:00
6543 added
LGTM-done
and removed
LGTM-need
labels 2019-11-23 16:59:56 +00:00
Member

this need future features/improvement but I think it is ready for merge

this need future features/improvement but I think it is ready for merge
6543 approved these changes 2019-11-23 17:00:45 +00:00
Dismissed
mmarif referenced this issue from a commit 2019-11-24 12:43:00 +00:00
mmarif closed this pull request 2019-11-24 12:43:00 +00:00
mmarif deleted branch 8-repo-pr-list 2019-11-24 12:43:28 +00:00
This repo is archived. You cannot comment on pull requests.
No reviewers
No Milestone
No Assignees
2 Participants
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: gitnex/GitNex#198
No description provided.