#161291020 Implement time to read an article

[darthrighteous]

What does this PR do?

Add the time to read an article to the article table

Description of Task to be completed?

• add a readTime column to the article table
• calculate the time taken to read an article and add to the article table

How should this be manually tested?

• clone the repo, checkout to this branch feature/161291020/calculate-time-to-read
• set up your local db and .env variables
• sign up a user using the sign up route
• create an article using the create article route
• see the calculated reading time in the response or query the db

Any background context you want to provide?

The readTime value is in microseconds. Transformations can be done on the front-end.

What are the relevant pivotal tracker stories?

161291020

Screenshots (if appropriate)

Articles table columns:

Read time of a created article:

Questions:

N/A

[coveralls]

Pull Request Test Coverage Report for Build 548

• 1 of 1 (100.0%) changed or added relevant line in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.009%) to 93.068%

---

Totals
Change from base Build 542:	0.009%
Covered Lines:	578
Relevant Lines:	600

---

💛 - Coveralls

[sulenchy]

I can see the stat.time is the reading time in milliseconds from readingTime package. I think having it in minutes would be a good idea so that whoever wants to consume the API can do that without any further manipulation.

[darthrighteous]

@sulenchy Thanks for the feedback. I thought about this and I think it's better to have the time in milliseconds so we have options on the front end. For example, if we wanted to display the seconds as well, not just the minutes. Considering the calculation isn't complex(simple division), I think doing on the frontend won't be an issue. What do you think?