Fix speech recognition example in documentation: button logic and error handling #20
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request addresses two issues in the speech recognition example code:
Fixed the button rendering logic:
Corrected the
recognizing
state in the conditional rendering of the Start/Stop button. The "Start" button now shows when not recognizing, and "Stop" when recognizing.Improved error handling in the
handleStart
function:Added try/catch block and made the function asynchronous to properly handle potential errors during permission request and speech recognition start.
These changes improve the accuracy and robustness of the documentation example, ensuring that developers can implement speech recognition in their Expo projects more reliably.
Testing:
Please take a look at these changes and let me know if you need any more changes.