Feature request (for later): Ability to mark an "issue" as OK
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 33
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
I don't know if anyone else might find this useful, but as I've been testing this "issues" feature with Matthew formatting (a long PDF), and I'm thinking it might be nice if there was a way mark places in the text as OK or "good enough" -- so the Issue feature wouldn't keep bothering the user about it.
This feature would be something to add later, as the current behavior is just starting to solidify. But eventually, it would be good to have a way to ignore certain pages, and then later be able to review the places ignored, or to unmark an ignored issue, so it becomes an issue again.
I can see this being useful in large publications (like Matthew or Gospels or NT etc.)
Just something to file away for later consideration.
Contributor guide
No contributing guide indexed for this repository
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. Start by locating the existing issues feature and reviewing how issues are displayed and tracked; done would require an agreed design for marking issues as acceptable, reviewing ignored locations, and restoring them as active issues.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100