fix(onboarding): Preserve user-entered project slug during platform selection

[sentry]

This PR addresses a bug where a user-entered project slug would be overwritten when a platform was selected during the project creation onboarding flow.

Problem:
Previously, the logic in handlePlatformChange attempted to determine if the project name was user-modified by comparing formData.projectName with formData.platform?.key. This heuristic was flawed:

1. If a user typed a project name that happened to match the currently selected platform's key, the system would incorrectly assume it was an auto-generated name and overwrite it if a different platform was subsequently selected.
2. The useEffect that synced initialData to formData could also inadvertently reset the projectName field if initialData re-evaluated (e.g., due to asynchronous loading of teams), clobbering user input.

Solution:

1. Introduced a useRef, hasUserModifiedProjectName, to explicitly track whether the user has manually typed into the project slug input field. This provides a reliable signal that the user intends to keep their custom name.
2. The onChange handler for the project name input now sets hasUserModifiedProjectName.current = true when the user types. It also resets this ref to false if the user clears the input, allowing the platform-based auto-fill to take over again.
3. handlePlatformChange now uses hasUserModifiedProjectName.current to decide whether to overwrite the projectName with the selected platform's ID, ensuring user input is respected.

Tests:
Added new test cases to createProject.spec.tsx to cover:

• Ensuring a user-entered name (even one matching a platform key) is preserved when switching platforms.
• Verifying that clearing the project name input allows platform selection to re-populate the field.

Ref NEW-769

[linear]

NEW-769 Onboarding renames project to “other” after selecting platform

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

[cursor]

Ref not reset when useEffect clobbers project name

Medium Severity

The hasUserModifiedProjectName ref can desync from actual form state. The existing useEffect (lines 247–251) resets formData.projectName to '' whenever initialData changes (e.g., when defaultTeam updates due to async team loading), but does not reset hasUserModifiedProjectName. After this, the ref is true while the project name is empty, so subsequent platform selection preserves the empty string instead of auto-filling the platform name — a regression from the old behavior which would auto-fill for empty names.

Additional Locations (2)

• static/app/views/projectInstall/createProject.tsx#L246-L251
• static/app/views/projectInstall/createProject.tsx#L445-L446

 

[cursor]

AutoFill project name overwritten on platform change

Low Severity

When autoFill is active (user navigated back from getting-started), the initialData pre-fills projectName from the previously created project (e.g., "my-cool-app"). However, hasUserModifiedProjectName starts as false and is only set true by typing in the input — not by programmatic pre-filling. So if the user changes the platform, handlePlatformChange treats the auto-filled name as auto-generated and overwrites it with the new platform key. The old heuristic (projectName !== platform.key) would have preserved it since the project name typically differs from the platform key.

Additional Locations (1)

• static/app/views/projectInstall/createProject.tsx#L194-L195