Skip to content

fix(patch): drop the dead first-run provider chooser from onboarding - #317

Open
HuangLeijiana wants to merge 1 commit into
dataelement:mainfrom
HuangLeijiana:pr/fix-patch-onboarding-dead-code
Open

fix(patch): drop the dead first-run provider chooser from onboarding#317
HuangLeijiana wants to merge 1 commit into
dataelement:mainfrom
HuangLeijiana:pr/fix-patch-onboarding-dead-code

Conversation

@HuangLeijiana

Copy link
Copy Markdown
Contributor

The settings-models patch rewrote the first-run dialog to advertise choosing among twelve providers ('Choose a provider and enter its API key'), added an ONBOARDING_PROVIDERS catalog and a selectedProvider state, but never rendered the chooser: setSelectedProvider has zero call sites and the onboardingProvider/onboardingManufacturer/… keys are never read. New users were locked to the default row (DeepSeek or whichever provider sorted first) while the copy promised a picker.

Revert the onboarding dialog to the upstream single-provider flow and copy (configures the default DeepSeek provider it actually shows) and remove the dead catalog/state/keys, keeping the real provider grid in the settings add-provider flow untouched. The patch was regenerated from pristine and verified: it applies cleanly and reproduces the edited artifact byte-for-byte. The patch test now asserts the dead code is gone instead of pinning its presence.

The settings-models patch rewrote the first-run dialog to advertise
choosing among twelve providers ('Choose a provider and enter its API
key'), added an ONBOARDING_PROVIDERS catalog and a selectedProvider
state, but never rendered the chooser: setSelectedProvider has zero
call sites and the onboardingProvider/onboardingManufacturer/… keys are
never read. New users were locked to the default row (DeepSeek or
whichever provider sorted first) while the copy promised a picker.

Revert the onboarding dialog to the upstream single-provider flow and
copy (configures the default DeepSeek provider it actually shows) and
remove the dead catalog/state/keys, keeping the real provider grid in
the settings add-provider flow untouched. The patch was regenerated
from pristine and verified: it applies cleanly and reproduces the
edited artifact byte-for-byte. The patch test now asserts the dead code
is gone instead of pinning its presence.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant