On Gitlab you can be the creator of an MR and be tagged as a reviewer and / or an assignee.
Gitlab documentation is not super clear on what exactly is the role of an Assignee. But it compares the Reviewer and the Assignee as: "In comparison to an Assignee, who is directly responsible for creating or merging a merge request, a Reviewer is a team member who may only be involved in one aspect of the merge request, such as a peer review."
Thus I think it is not rare that the creator of the MR is also tagged as the Assignee.
This MR filters out from the list of request, MRs created by the user. This generates noise in the "To Review" tab and is redundant information with the "Under Review" tab
I also took the opportunity to slightly improve the removeDuplicateObjectFromArray typings. By adding generic which will infer the output type from the param's type.
On Gitlab you can be the creator of an MR and be tagged as a reviewer and / or an assignee.
Gitlab documentation is not super clear on what exactly is the role of an Assignee. But it compares the Reviewer and the Assignee as: "In comparison to an Assignee, who is directly responsible for creating or merging a merge request, a Reviewer is a team member who may only be involved in one aspect of the merge request, such as a peer review." Thus I think it is not rare that the creator of the MR is also tagged as the Assignee.
This MR filters out from the list of request, MRs created by the user. This generates noise in the "To Review" tab and is redundant information with the "Under Review" tab
I also took the opportunity to slightly improve the
removeDuplicateObjectFromArraytypings. By adding generic which will infer the output type from the param's type.