Skip to content

Conversation

@aleksandernsilva
Copy link
Contributor

@aleksandernsilva aleksandernsilva commented Jun 26, 2025

Proposed changes (including videos or screenshots)

This pull request introduces a new Wizard component designed to simplify the creation of multi-step user flows. The component in its current state is minimal but flexible and controlled by a custom hook that manages the wizard's state.

Key features

  • State management: useWizard hook manages the entire state of the wizard, including current step and overall progress.
  • Component-Based: The wizard is broken down into smaller, optional, reusable components, each with a specific responsibility.

Hooks:

  • useWizard Takes a list of step metadata and returns an API for manipulating the wizard's state.
  • useWizardSteps Accepts a StepsLinkedList and provides a reactive array of StepNode objects.

Utility components

  • Wizard The main container component that receives the wizard API and provides it to all sub-components via context.
  • WizardContent A component that conditionally renders its children based on the current active step.
  • WizardTabs Renders a list of tabs that represent the steps in the wizard, handling navigation and disabled states.
  • WizardActions A layout component for wrapping and aligning navigation buttons.
  • WizardBackButton A button that navigates to the previous step. It is automatically disabled if there's no previous step.
  • WizardNextButton A button that navigates to the next step. It is automatically disabled there's no next step.

Issue(s)

CTZ-186
CTZ-188

Steps to test or reproduce

Further comments

@dionisio-bot
Copy link
Contributor

dionisio-bot bot commented Jun 26, 2025

Looks like this PR is not ready to merge, because of the following issues:

  • This PR is targeting the wrong base branch. It should target 7.10.0, but it targets 7.9.0

Please fix the issues and try again

If you have any trouble, please check the PR guidelines

@changeset-bot
Copy link

changeset-bot bot commented Jun 26, 2025

🦋 Changeset detected

Latest commit: b35711b

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 36 packages
Name Type
@rocket.chat/ui-client Minor
@rocket.chat/meteor Patch
@rocket.chat/gazzodown Major
@rocket.chat/ui-voip Major
@rocket.chat/fuselage-ui-kit Patch
@rocket.chat/livechat Patch
@rocket.chat/uikit-playground Patch
@rocket.chat/core-typings Patch
@rocket.chat/rest-typings Patch
@rocket.chat/api-client Patch
@rocket.chat/apps Patch
@rocket.chat/core-services Patch
@rocket.chat/cron Patch
@rocket.chat/ddp-client Patch
@rocket.chat/freeswitch Patch
@rocket.chat/http-router Patch
@rocket.chat/model-typings Patch
@rocket.chat/ui-avatar Patch
@rocket.chat/ui-contexts Patch
@rocket.chat/account-service Patch
@rocket.chat/authorization-service Patch
@rocket.chat/ddp-streamer Patch
@rocket.chat/omnichannel-transcript Patch
@rocket.chat/presence-service Patch
@rocket.chat/queue-worker Patch
@rocket.chat/stream-hub-service Patch
@rocket.chat/license Patch
@rocket.chat/omnichannel-services Patch
@rocket.chat/pdf-worker Patch
@rocket.chat/presence Patch
rocketchat-services Patch
@rocket.chat/models Patch
@rocket.chat/network-broker Patch
@rocket.chat/mock-providers Patch
@rocket.chat/ui-video-conf Patch
@rocket.chat/instance-status Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@github-actions
Copy link
Contributor

github-actions bot commented Jun 26, 2025

PR Preview Action v1.6.2

🚀 View preview at
https://RocketChat.github.io/Rocket.Chat/pr-preview/pr-36315/

Built to branch gh-pages at 2025-07-25 16:09 UTC.
Preview will be ready when the GitHub Pages deployment is complete.

@codecov
Copy link

codecov bot commented Jun 26, 2025

Codecov Report

❌ Patch coverage is 90.76923% with 30 lines in your changes missing coverage. Please review.
✅ Project coverage is 65.82%. Comparing base (02a555a) to head (b35711b).
⚠️ Report is 1 commits behind head on develop.

Additional details and impacted files

Impacted file tree graph

@@             Coverage Diff             @@
##           develop   #36315      +/-   ##
===========================================
+ Coverage    65.44%   65.82%   +0.38%     
===========================================
  Files         3094     3188      +94     
  Lines       105157   106906    +1749     
  Branches     19999    20395     +396     
===========================================
+ Hits         68816    70374    +1558     
- Misses       33732    33855     +123     
- Partials      2609     2677      +68     
Flag Coverage Δ
e2e 58.12% <ø> (+1.16%) ⬆️
unit 70.95% <90.76%> (+0.12%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@aleksandernsilva aleksandernsilva marked this pull request as ready for review July 9, 2025 00:14
@aleksandernsilva aleksandernsilva requested a review from a team as a code owner July 9, 2025 20:14
@tassoevan tassoevan force-pushed the feat/wizard branch 2 times, most recently from 8a0a97e to 2baf055 Compare July 12, 2025 03:36
tassoevan
tassoevan previously approved these changes Jul 17, 2025
@tassoevan tassoevan added the stat: QA assured Means it has been tested and approved by a company insider label Jul 25, 2025
@dionisio-bot dionisio-bot bot added the stat: ready to merge PR tested and approved waiting for merge label Jul 25, 2025
@kodiakhq kodiakhq bot merged commit a1c99df into develop Jul 25, 2025
49 checks passed
@kodiakhq kodiakhq bot deleted the feat/wizard branch July 25, 2025 16:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

stat: QA assured Means it has been tested and approved by a company insider stat: ready to merge PR tested and approved waiting for merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants