'reading_time' parameter not returned when used in 'fields' query of Ghost Content API
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 134
- Forks
- 87
- Avg merge
- 12m
- Merged PRs (30d)
- 25
Description
Issue Summary:
When using the Ghost Content API, specifically the "/posts/" or "/pages/" endpoints with the "field" query parameter to specify the fields to be returned, the "reading_time" parameter does not function as expected. While other parameters work fine, attempting to limit the fields returned by including "reading_time" results in unexpected behavior.
To Reproduce:
- Make a request to the "/posts/" or "/pages/" endpoint of the Ghost Content API.
- Include the "field" query parameter with the value of "reading_time" to limit the fields returned to just the reading time.
- Observe that the response does not return "reading_time".
Technical details:
- Ghost Version: 5.80.0
- Node Version: Unknown
- Environment: Production
- Browser/OS: Not relevant
- Database: MySQL 8
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Ghost Content API request against the /posts/ and /pages/ endpoints with field=reading_time, then compare its response with a request selecting another field. Done means reading_time is returned when it is included in the field query parameter.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100