Clean up global rateLimitSeconds & fully shift to provider version

[ross]

Context

This PR bundles fixes & cleanup around rateLimitSeconds after https://github.com/RooVetGit/Roo-Code/pull/2376/files 🚢ed.

Implementation

The first commit shifts things to be soley driven off of the provider-specific version of rateLimitSeconds and can be found in 54b8e84. It also removes an unnecessary default value. This commit should have no user visible impact and is intended to make things more directly tied to the value's new location.

The second makes a pass through things removing all of the references to the original global rateLimitSeconds with the exception of the settings value itself since that needs to live on for now so that it can be migrated to the provider specific field 2151b5f. Afaik this commit should have no meaningful impact on the extension.

Screenshots

No user visible changes are intended.

How to Test

(copied from #2376 (comment))

Set a rate-limit in the advanced section before updating to this code. Update and see that the value you set is copied over to all of your profiles. You can then go into each profile and change the values to something that makes sense for the specific provider. Once saved the value should be tied to the provider.

If no value is set before you update, e.g. 0s, that 0s value will be copied to all the profiles as well.

Get in Touch

rwmcfa1

/cc #2376 as realted

---

Important

Refactor to remove global rateLimitSeconds and shift to provider-specific configuration.

• Configuration Changes:
  • Remove global rateLimitSeconds from roo-code-defaults.ts and ClineProvider.ts.
  • Update Cline.ts to use apiConfiguration?.rateLimitSeconds instead of global rateLimitSeconds.
• State Management:
  • Remove rateLimitSeconds handling from webviewMessageHandler.ts and ExtensionStateContext.tsx.
  • Update ExtensionMessage.ts and WebviewMessage.ts to remove rateLimitSeconds references.
• Testing:
  • Update ClineProvider.test.ts to remove tests related to rateLimitSeconds.

^{This description was created by for 2151b5f. It will automatically update as commits are pushed.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: 43bbf84

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

[ross]

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.

Not sure if this one needs a changeset or not. It's definitely a patch-level change, but doesn't really have anything that I think would warrant mention in the CHANGELOG.

[mrubens]

🚀