microsoft / microsoft/vscode-github-issue-notebooks
Have a way to control the number of issues shown above the fold
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 237
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
While it's great that the output is naturally truncated, being able to restrict more would be handy. For instance, when looking at the move upvoted issues in a repo, it would be great to just cap it at say 5 and have the rest be under Show ... more. This could also allow for queries where making sure you view all issues no matter how many possible by setting a high enough number to show.
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
No files, tests, or entry points are named in the issue. Start by tracing the TypeScript code that renders GitHub issue notebook results and handles output truncation, then define the setting or query option and its interaction with “Show ... more”; done means users can cap visible issues or choose a high enough limit to view all results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100