Seperate unread setting for each view
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 39k
- Forks
- 2.1k
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 10
Description
Clear and concise description of the problem
Now we have a global "general>unread" setting to decide when to "mark as read." However, there should be different rules for different views. For example, I'd like to use "hover to mark as read" for social media or images, while I prefer not to use "hover to mark as read" for articles or videos.
Suggested solution
Allowing seperate unread setting for each view.
Alternative
No response
Additional context
No response
Validations
- Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
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 locating the existing global “general > unread” setting and the code that applies “mark as read” rules for each view. The feature is done when unread behavior can be configured independently for different views, including hover-to-mark-as-read choices for social media, images, articles, and videos.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100