Skip to content

refactor: rename GetUpdatedSelfTeamUseCase to SyncSelfTeamInfoUseCase [WPB-21894]#4570

Open
MohamadJaara wants to merge 1 commit intodevelopfrom
mo/fix/self-profile-screen-is-waiting-for-api-request
Open

refactor: rename GetUpdatedSelfTeamUseCase to SyncSelfTeamInfoUseCase [WPB-21894]#4570
MohamadJaara wants to merge 1 commit intodevelopfrom
mo/fix/self-profile-screen-is-waiting-for-api-request

Conversation

@MohamadJaara
Copy link
Member

@MohamadJaara MohamadJaara commented Feb 5, 2026

https://wearezeta.atlassian.net/browse/WPB-21894


PR Submission Checklist for internal contributors

  • The PR Title

    • conforms to the style of semantic commits messages¹ supported in Wire's Github Workflow²
    • contains a reference JIRA issue number like SQPIT-764
    • answers the question: If merged, this PR will: ... ³
  • The PR Description

    • is free of optional paragraphs and you have filled the relevant parts to the best of your ability

What's new in this PR?

Issues

getting user self team info is always waiting on a remote sync of the team data which can block some screens from loading untill we have the whole informations

Solutions

in almost all cases where we need self team we also need self user and there is already a use case for this
also add a seperated usecase for the sync of self team in case we need to trigger it in async in some screens


PR Post Submission Checklist for internal contributors (Optional)

  • Wire's Github Workflow has automatically linked the PR to a JIRA issue

PR Post Merge Checklist for internal contributors

  • If any soft of configuration variable was introduced by this PR, it has been added to the relevant documents and the CI jobs have been updated.

References
  1. https://sparkbox.com/foundry/semantic_commit_messages
  2. https://github.com/wireapp/.github#usage
  3. E.g. feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764.

@sonarqubecloud
Copy link

sonarqubecloud bot commented Feb 5, 2026

@codecov
Copy link

codecov bot commented Feb 5, 2026

Codecov Report

❌ Patch coverage is 96.87500% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 48.54%. Comparing base (3b69d2e) to head (c6eaeeb).

Files with missing lines Patch % Lines
...oid/ui/home/settings/account/MyAccountViewModel.kt 90.00% 0 Missing and 1 partial ⚠️
Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #4570      +/-   ##
===========================================
+ Coverage    48.50%   48.54%   +0.04%     
===========================================
  Files          575      575              
  Lines        19810    19821      +11     
  Branches      3312     3308       -4     
===========================================
+ Hits          9608     9622      +14     
  Misses        9187     9187              
+ Partials      1015     1012       -3     
Files with missing lines Coverage Δ
...tions/details/GroupConversationDetailsViewModel.kt 89.43% <100.00%> (+2.65%) ⬆️
...id/ui/userprofile/self/SelfUserProfileViewModel.kt 58.04% <100.00%> (+1.52%) ⬆️
...oid/ui/home/settings/account/MyAccountViewModel.kt 89.83% <90.00%> (+0.73%) ⬆️

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3b69d2e...c6eaeeb. Read the comment docs.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants