Feat: Add a new button to import settings on the welcome screen

[julionav]

Context

Right now you cannot import your settings into roo without adding a new API key #2208

Implementation

• Added new button to WelcomeView.tsx that starts the import settings process

• Updated import logic to set a provider in the ContextProxy. This was required to allow the app to stop showing the welcome screen.

  • For some reason there are 2 places holding the API configs. ContextProxy and ProviderSettingsManager -- I guess is code from Cline. Without the proivider in ContextProxy the app thinks that no api has been configured, even though there are several API config in the provider

Screenshots

before	after

How to Test

Get in Touch

Discord: profotium

---

Important

Add "Import Settings" button to welcome screen and update import logic to handle provider settings in ContextProxy.

• UI Changes:
  • Added "Import Settings" button to WelcomeView.tsx.
• Import Logic:
  • Updated importSettings in importExport.ts to set provider settings in ContextProxy.
• Translations:
  • Added "Import Settings" translation in welcome.json for multiple languages including en, es, fr, de, zh-CN, zh-TW, hi, it, pl, pt-BR, vi, and ca.

^{This description was created by for 6765bdd. You can customize this summary. It will automatically update as commits are pushed.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: 9921bf5

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

[mrubens]

@cte do you mind taking a look at this? Agree that it makes sense to allow for settings import on the welcome screen somehow. Thanks!

[adamhill]

I think it should be more part of the onboarding flow (maybe a 2nd "OR" block, since it would pull in your keys too)

wdyt @sachasayan @elianiva

[elianiva]

i prefer having something that's more visible, like a second OR block or some sort like Adam said

currently it's using small text and users might miss them—due to themes and whatnot

also having it on a separate section aligns with what we have now, so it'll give the impression of

• you're new? try using requesty or openrouter for a start
• you've dabbled in before? cool, you can bring your own api key using this menu
• oh you've done this before? gotcha, use this button to import your old stuff

at the moment i feel like it gives the impression of psst, here's the import settings button due to it being small

we can also add some explanations if we decide to add it on its own section, like "importing settings will NOT import your api key" or something like that
it helps setting the users expectation on what this "import settings" button actually do

[sachasayan]

This is great and I'm fine with merging it as-is and doing another pass for UI improvements later. I agree this is a screen which could use some more love and I think a dedicated PR for that is best.

Could you fix the failing tests, @julionav?

Also, for anyone who knows: How much complexity is there in removing the provider from the proxy and keeping providerSettingsManager as source of truth for apiConfig, as mentioned in the code?