speced / speced/respec

marking closed github issues

Open
#4,097 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Feature request High priority
Dominant language
JavaScript
Stars
806
Forks
434
Avg merge
1d 21h
Merged PRs (30d)
32

Description

Is your feature request related to a problem? Please describe.

If an issue is closed at github, the associated issue link generated by <div class="issue" data-number="271"></div> marks this with a strikeout, but the issue list generated by <section id="issue-summary"></section> does not.

Describe the solution you'd like

Would it be possible to strike out or otherwise style closed issues differently in the issue summary?

(Psychologically I'd like to see WG is getting closer to the end game, and the list was getting shorter:-)

Additional context
Add any other context or screenshots about the feature request here.

I'm tempted to request a configuration option such that closed isses are not listed at all, not making an issue box and not being in the summary list, so that closing the issues at github is enough to generate a clean document with no issue boxes. I'm not sure if I'd use that until I'd tried it though. However marking closed issues in the issue summary would already help locate the closed issues then take a decision on whether to remove the issue div from the document.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the code that generates the issue summary from

and compare it with the handling of issue links such as . Done means closed GitHub issues are visibly struck out or otherwise styled differently in the summary.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
documentation
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.