Skip to content

feat: list of call participants [WPB-1057]#4762

Open
saleniuk wants to merge 20 commits intodevelopfrom
feat/call-participants-list
Open

feat: list of call participants [WPB-1057]#4762
saleniuk wants to merge 20 commits intodevelopfrom
feat/call-participants-list

Conversation

@saleniuk
Copy link
Copy Markdown
Contributor

@saleniuk saleniuk commented Apr 27, 2026

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


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

As a Wire user on new Android I want to be able to see who is in the group call.

Solutions

Implemented a ParticipantList which consists of ParticipantItem, and added it to the draggable bottom sheet of OngoingCallScreen.

Dependencies (Optional)

Needs releases with:

Testing

How to Test

Start or join a call and open the bottom sheet (drag or click on the handle).

Attachments (Optional)

Screen_recording_20260427_150423.mp4
Screen_recording_20260427_163714.mp4
image

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.

@saleniuk saleniuk changed the base branch from feat/calling-controls-as-bottom-sheet to develop April 27, 2026 15:53
@pull-request-size pull-request-size Bot added size/L and removed size/S labels Apr 27, 2026
@codecov
Copy link
Copy Markdown

codecov Bot commented Apr 30, 2026

Codecov Report

❌ Patch coverage is 50.00000% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 51.00%. Comparing base (27fd364) to head (0d94a5a).

Files with missing lines Patch % Lines
...alling/ongoing/participantslist/ParticipantItem.kt 0.00% 1 Missing ⚠️

❌ Your patch check has failed because the patch coverage (50.00%) is below the target coverage (80.00%). You can increase the patch coverage or adjust the target coverage.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #4762      +/-   ##
===========================================
- Coverage    51.00%   51.00%   -0.01%     
===========================================
  Files          605      606       +1     
  Lines        20996    20998       +2     
  Branches      3388     3388              
===========================================
+ Hits         10709    10710       +1     
- Misses        9281     9282       +1     
  Partials      1006     1006              
Files with missing lines Coverage Δ
...wire/android/ui/calling/model/UICallParticipant.kt 100.00% <100.00%> (ø)
...alling/ongoing/participantslist/ParticipantItem.kt 0.00% <0.00%> (ø)

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 27fd364...0d94a5a. Read the comment docs.

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

…ants-list

# Conflicts:
#	app/src/main/kotlin/com/wire/android/ui/calling/ongoing/OngoingCallScreen.kt
modifier = Modifier
.fillMaxWidth()
.height(0.dp)
.zIndex(1f) // ensure the section header is above the participant items when scrolled
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Instead of of simulating sticky header, can use LazyColum with stickyHeader

 LazyColumn {
    stickyHeader {
        SectionHeader(...)
    }
    items(...) { ... }
}

Copy link
Copy Markdown
Contributor Author

@saleniuk saleniuk May 4, 2026

Choose a reason for hiding this comment

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

It's not simulating the sticky header, it's actually a different intention than a sticky header. It handles the visuals of the whole list scroll, so it cannot be a part of the list as a sticky header, it needs to stay above the list, so in column it will be drawn first, that's why zIndex is used so that the background of the list doesn't cover the shadow elevation that this element creates.

@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud Bot commented May 4, 2026

@saleniuk saleniuk requested a review from ohassine May 4, 2026 09:50
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