FIX: Initialize tts speed state in ClineProvider

[heyseth]

Context

I forgot to initialize the tts speed state in ClineProvider.ts. As a result the tts speed setting would default to 100% and the user would have to reconfigure the setting on each editor load.

Implementation

this.getState().then(({ ttsSpeed }) => {
     setTtsSpeed(ttsSpeed ?? 1)
})

How to Test

1. Run your usual testing environment and navigate to Settings > Notifications > Enable text-to-speech > Speed

2. Set the value of speed to a non-default value.
3. Close the testing environment.
4. Reopen testing environment.
5. Run a Roo Code task, verify that the tts speed is reflecting the saved value from before.

Get in Touch

I can be reached at @ocean.smith on discord.

---

Important

Initialize TTS speed state in ClineProvider.ts to use saved value or default to 100%.

• Behavior:
  • Initialize TTS speed state in ClineProvider to use saved value or default to 100%.
• Implementation:
  • Added this.getState().then(({ ttsSpeed }) => { setTtsSpeed(ttsSpeed ?? 1) }) in ClineProvider.ts to initialize TTS speed.

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

[changeset-bot]

⚠️ No Changeset found

Latest commit: a1a0eed

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

[heyseth]

@mrubens I somehow missed this during testing sorry!