Skip to content

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

Open
saleniuk wants to merge 10 commits into
developfrom
feat/start-or-schedule-a-meeting-destination
Open

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

Conversation

@saleniuk
Copy link
Copy Markdown
Contributor

@saleniuk saleniuk commented Jun 3, 2026

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
Copy link
Copy Markdown

codecov Bot commented Jun 4, 2026

Codecov Report

❌ Patch coverage is 0% with 19 lines in your changes missing coverage. Please review.
✅ Project coverage is 49.57%. Comparing base (434f0b5) to head (8e52a5d).

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.61%   49.57%   -0.05%     
===========================================
  Files          644      646       +2     
  Lines        22562    22581      +19     
  Branches      3443     3443              
===========================================
  Hits         11195    11195              
- Misses       10327    10346      +19     
  Partials      1040     1040              
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 434f0b5...8e52a5d. Read the comment docs.

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

@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud Bot commented Jun 4, 2026

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.

3 participants