Skip to content

feat(meetings): start or schedule a meeting screen destination and layout [WPB-25046]#4922

Merged
saleniuk merged 12 commits into
developfrom
feat/start-or-schedule-a-meeting-destination
Jun 8, 2026
Merged

feat(meetings): start or schedule a meeting screen destination and layout [WPB-25046]#4922
saleniuk merged 12 commits into
developfrom
feat/start-or-schedule-a-meeting-destination

Conversation

@saleniuk

@saleniuk saleniuk commented Jun 3, 2026

Copy link
Copy Markdown
Contributor

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


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?

New screen for creating meeting, both scheduled and meet now.
This PR contains a navigation graph for new meetings flow, new destination and base layout. For now, the base layout contains only the title input, more will be implemented in the following PRs.
Also, added default content description for bottom sheet drag handle.

Testing

How to Test

Open dev build > Meetings > New > choose "Meet now" or "Schedule".

Attachments (Optional)

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 and others added 6 commits June 3, 2026 16:03
@codecov

codecov Bot commented Jun 4, 2026

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 0% with 19 lines in your changes missing coverage. Please review.
✅ Project coverage is 49.28%. Comparing base (50641c4) to head (e906fa3).

Files with missing lines Patch % Lines
...id/feature/meetings/ui/create/NewMeetingNavArgs.kt 0.00% 12 Missing ⚠️
.../feature/meetings/ui/create/NewMeetingViewModel.kt 0.00% 6 Missing ⚠️
...id/feature/meetings/ui/MeetingsViewModelFactory.kt 0.00% 1 Missing ⚠️

❌ Your patch check has failed because the patch coverage (0.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    #4922      +/-   ##
===========================================
- Coverage    49.32%   49.28%   -0.05%     
===========================================
  Files          646      648       +2     
  Lines        22891    22910      +19     
  Branches      3503     3503              
===========================================
  Hits         11291    11291              
- Misses       10553    10572      +19     
  Partials      1047     1047              
Files with missing lines Coverage Δ
...roid/feature/meetings/ui/MeetingsViewModelGraph.kt 0.00% <ø> (ø)
...id/feature/meetings/ui/MeetingsViewModelFactory.kt 0.00% <0.00%> (ø)
.../feature/meetings/ui/create/NewMeetingViewModel.kt 0.00% <0.00%> (ø)
...id/feature/meetings/ui/create/NewMeetingNavArgs.kt 0.00% <0.00%> (ø)

Continue to review full report in Codecov by Harness.

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

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

@sonarqubecloud

sonarqubecloud Bot commented Jun 8, 2026

Copy link
Copy Markdown

@saleniuk saleniuk added this pull request to the merge queue Jun 8, 2026
Merged via the queue into develop with commit ed57150 Jun 8, 2026
21 of 22 checks passed
@saleniuk saleniuk deleted the feat/start-or-schedule-a-meeting-destination branch June 8, 2026 16:11
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.

4 participants