We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi! 馃憢
Firstly, thanks for your work on this project! 馃檪
Today I used patch-package to patch react-native-tts@4.1.0 for the project I'm working on.
react-native-tts@4.1.0
Here is the diff that solved my problem:
diff --git a/node_modules/react-native-tts/index.d.ts b/node_modules/react-native-tts/index.d.ts index 3073395..7ce70ca 100644 --- a/node_modules/react-native-tts/index.d.ts +++ b/node_modules/react-native-tts/index.d.ts @@ -94,7 +94,7 @@ export class ReactNativeTts extends RN.NativeEventEmitter { setDefaultRate: (rate: number, skipTransform?: boolean) => Promise<"success">; setDefaultPitch: (pitch: number) => Promise<"success">; setDefaultLanguage: (language: string) => Promise<"success">; - setIgnoreSilentSwitch: (ignoreSilentSwitch: boolean) => Promise<boolean>; + setIgnoreSilentSwitch: (ignoreSilentSwitch: 'ignore' | 'inherit' | 'obey') => Promise<boolean>; voices: () => Promise<Voice[]>; engines: () => Promise<Engine[]>; /** Read the sentence and return an id for the task. */ @@ -105,7 +105,7 @@ export class ReactNativeTts extends RN.NativeEventEmitter { addEventListener: <T extends TtsEvents>( type: T, handler: TtsEventHandler<T> - ) => void; + ) => RN.EmitterSubscription; removeEventListener: <T extends TtsEvents>( type: T, handler: TtsEventHandler<T>
This issue body was partially generated by patch-package.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi! 馃憢
Firstly, thanks for your work on this project! 馃檪
Today I used patch-package to patch
react-native-tts@4.1.0
for the project I'm working on.Here is the diff that solved my problem:
This issue body was partially generated by patch-package.
The text was updated successfully, but these errors were encountered: