You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the ReadingTime calculation in can return 0 minutes, which is not accurate as even a short post would at least be closer to 1 minute to read. Therefore, we should update the calculated minutes time formatting to always be at least one minute.
Steps to Reproduce
Create a post with a very short amount of content (e.g. a few sentences).
Run the ReadingTime calculation on the post.
Note that the calculated time may be 0 minutes.
Expected Behavior
The ReadingTime calculation should always return a minimum of 1 minute, even for very short posts.
Actual Behavior
The ReadingTime calculation can return 0 minutes, which is not accurate.
Possible Solution
Update the ReadingTime calculation to always add 1 to the calculated minutes time.
Credit
Thanks to @rgasch for bringing this issue to my attention.
The text was updated successfully, but these errors were encountered:
caendesilva
changed the title
Change the ReadTime calculation to never be under one minute
ReadTime calculation should never be under one minute
Mar 14, 2023
caendesilva
changed the title
ReadTime calculation should never be under one minute
ReadingTime calculation should never be under one minute
Mar 14, 2023
Issue Description
Currently, the
ReadingTime
calculation in can return 0 minutes, which is not accurate as even a short post would at least be closer to 1 minute to read. Therefore, we should update the calculated minutes time formatting to always be at least one minute.Steps to Reproduce
ReadingTime
calculation on the post.Expected Behavior
The
ReadingTime
calculation should always return a minimum of 1 minute, even for very short posts.Actual Behavior
The
ReadingTime
calculation can return 0 minutes, which is not accurate.Possible Solution
Update the
ReadingTime
calculation to always add 1 to the calculated minutes time.Credit
Thanks to @rgasch for bringing this issue to my attention.
The text was updated successfully, but these errors were encountered: