Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add async functions to IMembersClient and other changes #651

Closed
wants to merge 23 commits into from

Conversation

belcher-rok
Copy link
Contributor

@belcher-rok belcher-rok commented Mar 20, 2024

  • Improve Create Group and Create User mock to better emulate GitLab.
  • Add support for explicit Group Path in mock helpers.
  • Add IUserClient.GetByUserNameAsync
  • Add RemoveMemberFrom*Async and Implement async versions of the other Group and Project methods.
  • Add unit and integrations tests to verify behavior of both the GitHub and Mock IMembersClient.

@belcher-rok belcher-rok requested a review from a team as a code owner March 20, 2024 02:08
@belcher-rok belcher-rok requested review from louis-z and removed request for a team March 20, 2024 02:08
@belcher-rok
Copy link
Contributor Author

@louis-z Do you know why the list of commits in this PR includes all the commits from my previous PR? What am I not doing correctly?

@@ -158,8 +160,10 @@ public Models.User Update(int id, UserUpsert userUpsert)
var user = Server.Users.GetById(id);
if (user != null)
{
user.Name = userUpsert.Name;
user.Email = userUpsert.Email;
// user.UserName = userUpsert.Username ?? user.UserName; // TODO
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there an reason of why the username can't be updated like the others?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Toa741 NGitLab.Mock.User.UserName is not settable. I assumed there is a reason for this, I just didn't have the time or need to investigate right now.

@louis-z
Copy link
Member

louis-z commented Mar 21, 2024

@louis-z Do you know why the list of commits in this PR includes all the commits from my previous PR? What am I not doing correctly?

There are a few things to look out for:

  • Never work directly in the main branch, even if it is in your own fork.
  • When starting to work on an issue,
    • make sure to fetch the latest changes from the original repo
    • create a new dev branch from that repo's main branch, not your fork's (unless you previously synced those 2 main branches)

@belcher-rok
Copy link
Contributor Author

Replaced by PR #652.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants