GitHub issue not processed properly with readability
Open
Nobody has claimed this yet.
has-website-testcase
reader-mode-has-issues
- Dominant language
- JavaScript
- Stars
- 11.5k
- Forks
- 732
- PR merge metrics
- No merged PRs in 30d
Description
Example page: https://github.com/bluedotimpact/bluedot/issues/965
Expected: The title, comments and key metadata e.g. labels are extracted
Actual: only the first comment contents is extracted. This misses the issue title, labels, activity or further comments.
Example page output
<div id="readability-page-1" class="page">
<div data-testid="markdown-body" data-team-hovercards-enabled="true" data-turbolinks="false" id="issue-body-viewer">
<p dir="auto"> The old course hub is hosted at: </p>
<p dir="auto">
<a href="https://course.bluedot.org/" rel="nofollow">https://course.bluedot.org/</a>
</p>
<p dir="auto"> We should set up redirects with nginx that direct people to all the right places (e.g. <code>https://course.bluedot.org/home/alignment</code> -> <code>https://bluedot.org/courses/alignment</code>, and others) </p>
</div>
</div>
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 issue with the linked GitHub example page and inspecting the Readability output shown in the report. Trace why extraction stops at the first comment, then verify that the title, labels, activity, and all comments are included in the processed result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100