Skip to content

feat(FR-2684): migrate Deploy buttons to [Deploy | ▼] split using useDeploymentLauncher#6928

Closed
agatha197 wants to merge 5 commits into
04-22-feat_fr-2681_add_deploymentdetailpage_with_header_configuration_overview_and_4_tabsfrom
04-22-feat_fr-2684_migrate_deploy_buttons_to_deploy_split_using_usedeploymentlauncher
Closed

feat(FR-2684): migrate Deploy buttons to [Deploy | ▼] split using useDeploymentLauncher#6928
agatha197 wants to merge 5 commits into
04-22-feat_fr-2681_add_deploymentdetailpage_with_header_configuration_overview_and_4_tabsfrom
04-22-feat_fr-2684_migrate_deploy_buttons_to_deploy_split_using_usedeploymentlauncher

Conversation

@agatha197
Copy link
Copy Markdown
Contributor

resolves #NNN (FR-MMM)

Checklist: (if applicable)

  • Documentation
  • Minium required manager version
  • Specific setting for review (eg., KB link, endpoint or how to setup)
  • Minimum requirements to check during review
  • Test case(s) to demonstrate the difference of before/after

Copy link
Copy Markdown
Contributor Author

agatha197 commented Apr 22, 2026

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more


How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

  • flow:merge-queue - adds this PR to the back of the merge queue
  • flow:hotfix - for urgent changes, fast-track this PR to the front of the merge queue

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has required the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Apr 22, 2026

Coverage report for ./react

St.
Category Percentage Covered / Total
🔴 Statements
8.27% (-0.01% 🔻)
1757/21240
🔴 Branches
7.6% (-0.02% 🔻)
1131/14877
🔴 Functions
4.97% (-0% 🔻)
285/5735
🔴 Lines
8% (-0% 🔻)
1649/20603

Test suite run success

856 tests passing in 39 suites.

Report generated by 🧪jest coverage report action from 257797e

@agatha197 agatha197 changed the base branch from 04-22-feat_fr-2683_add_usedeploymentlauncher_hook_for_quick_deploy to graphite-base/6928 April 22, 2026 14:02
@agatha197 agatha197 force-pushed the 04-22-feat_fr-2684_migrate_deploy_buttons_to_deploy_split_using_usedeploymentlauncher branch from d69ad66 to 6509cb5 Compare April 22, 2026 14:02
This was referenced Apr 22, 2026
Extends the FR-2684 launcher migration to VFolderDeployModal.
When supportsQuickDeploy (manager 26.4.3+), the Deploy button becomes a
Space.Compact split button: primary fires deployVfolderV2 with the
selected preset/resource group, and the ▼ dropdown item calls
openLauncher({ modelFolderId }) to navigate to /deployments/new?model=<id>
for full configuration. Older managers fall back to the single Deploy button.
@agatha197 agatha197 changed the base branch from graphite-base/6928 to 04-22-feat_fr-2681_add_deploymentdetailpage_with_header_configuration_overview_and_4_tabs April 23, 2026 01:31
@github-actions github-actions Bot added size:L 100~500 LoC and removed size:M 30~100 LoC labels Apr 23, 2026
…o review step

When the user clicks the '...' dropdown item in VFolderDeployModal,
openLauncher now forwards resourceGroup and resourcePresetId as URL params
alongside the existing model param, and sets step=review so the launcher
opens directly on the review page with all fields pre-filled.

DeploymentLauncherCreateView parses the new params; preFilledModel prop
is replaced by preFilledValues (Partial<DeploymentLauncherFormValue>) to
accommodate the expanded field set cleanly.
Two root causes fixed:

1. ReviewSummary had 'use memo' — the React Compiler memoized it on the
   stable `form` reference, so shouldUpdate re-renders were bailed out
   even after form.setFieldsValue() set the pre-fill values. Removed
   'use memo' so shouldUpdate correctly re-renders the summary.

2. Pre-fill params (resourceGroup, resourcePresetId) were read in
   DeploymentLauncherCreateView via searchParams and passed as props,
   which was fragile across Suspense boundaries. Now DeploymentLauncherPageContent
   reads all pre-fill params directly via nuqs useQueryStates so nuqs
   tracks and preserves them across step navigation URL updates.
   preFilledValues prop removed; prop drilling eliminated.
@agatha197
Copy link
Copy Markdown
Contributor Author

Consolidated into grouped PR stack (Foundation/Components/Launcher/List/Detail). Closing this individual PR.

@agatha197 agatha197 closed this Apr 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:i18n Localization area:ux UI / UX issue. size:L 100~500 LoC

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant