Skip to content

fix(project-creation): Preserve SCM details on platform change - #122470

Open
jaydgoss wants to merge 8 commits into
masterfrom
fix/scm-platform-preserve-details
Open

fix(project-creation): Preserve SCM details on platform change#122470
jaydgoss wants to merge 8 commits into
masterfrom
fix/scm-platform-preserve-details

Conversation

@jaydgoss

Copy link
Copy Markdown
Member

TLDR

Keep SCM project names and team selections when users change platforms. Untouched project names still follow the selected platform default.

Details

ScmPlatformFeaturesCore previously cleared the entire project-details form on every platform selection. The project creation host now resets only an unmodified platform-derived name and preserves the selected team, alert settings, and manual names. It also persists whether the name was manually edited so the behavior remains stable after returning from getting-started.

Fixes VDY-183

Keep user-selected teams and manually edited project names when the SCM platform changes. Continue updating untouched project names from the platform default.

Fixes VDY-183
@linear-code

linear-code Bot commented Aug 24, 2026

Copy link
Copy Markdown

VDY-183

@github-actions github-actions Bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Aug 24, 2026
Use one compatibility rule when changing platforms and saving the SCM wizard. This keeps sessions from before the flag from losing their explicit project name after an unchanged return.

Refs VDY-183
The host no longer clears the whole form on a platform change; it only resets an untouched name. Update the derivation comment's example to match.
A restored session with wasNameManuallyModified: false is the one case where the persisted flag overrides the legacy explicit-name fallback. Pin that a platform change after the return re-derives the name and keeps the team.
Name the platform-change reset condition positively (shouldResetName) and replace the mixed ?? / !== expression in isProjectNameManuallyModified with explicit early returns. No behavior change.
The test retypes a name identical to the derived default, which reads as an accident. Comment the two phases and the deliberate identical retype: manual detection must come from the edit flag, not a value-vs-default comparison.
…m test

Retyping the derived default made the manual-edit phase invisible in the field. Type 'my-app' instead, so the preserved value can only come from the manual edit.
Select framework SDKs (Django/React) in the platform-change test so picks commit straight from the picker instead of detouring through the framework-suggestion modal, and assert the derived name before the switch so the re-derivation reads as a change.
@jaydgoss
jaydgoss marked this pull request as ready for review August 24, 2026 16:59
@jaydgoss
jaydgoss requested a review from a team as a code owner August 24, 2026 16:59
@jaydgoss
jaydgoss requested a review from a team August 24, 2026 17:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants