Don't show completed tasks as crossed-out / struck through
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- javascript
- Domain
- frontend
Research direction
No source file or test is identified in the issue. Start by locating where completed checkbox-list items are rendered and styled in the Tasks app, then compare the current presentation with the examples; done means completed tasks remain readable without strike-through, with the required configurability clarified and covered by tests.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
Completed tasks are struck through plus greyed out, therefore pretty hard to read. In many cases it is still important information to see which tasks have been completed.
Describe the solution you'd like
Please change the style from "strike through + greyed out" to just "checked" and maybe "slightly greyed out", so the items are easier to read. This should be at least configurable.
Describe alternatives you've considered
I have searched for - but not found the option to - configure this.
Additional context
I have opened a related feature request in the /text repository, as the same behaviour is present in the Nextcloud text editor with To-Do / checkbox lists. I don't know in which way this is connected.
Here are examples of how checkbox lists are formated in several projects:
Nextcloud 33.0.0 (Tasks 0.17.1)
- Dominant language
- JavaScript
- Stars
- 710
- Forks
- 125
- Avg merge
- 19h 37m
- Merged PRs (30d)
- 12
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from nextcloud/tasks
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
nextcloud/tasks#3240 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
nextcloud/tasks#3111 · 1 comment ·
Maintainers usually reply within 1 day
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
nextcloud/tasks#122 · 9 comments · 25 reactions ·
Maintainers usually reply within 1 day
-
1. to develop
Difficulty 5/5 Over a week Newbie friendliness 39/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
remotion-dev/remotion#13341 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
svix/svix-webhooks#2808 ·
Maintainers usually reply within 1 day
-
enhancement should-have ux
Difficulty 2/5 1-3 hours Newbie friendliness 72/100