Fix:Updated the WPM calculation logic #2
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 an issue where the displayed Words Per Minute (WPM) was erroneously showing as 0, failing to reflect the actual typing speed. The problem stemmed from incorrect initialization of startTime and endTime variables and inadequate state updates for WPM calculation.
To resolve this issue, I've implemented crucial updates to the WPM calculation logic. This includes ensuring proper initialization of startTime and endTime variables, correcting the calculation process based on the time taken and word count, and ensuring accurate state updates to reflect the calculated WPM.
With these changes, the WPM display now accurately reflects the user's typing speed
Before Changes:
After Changes: