QoL: Visualize Dateranges within the Datepicker
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 67/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript
- Domain
- frontend
Research direction
Start by locating the client-side datepicker and the existing handling for start and end dates, then inspect how the newer date-string ranges are represented. The work is done when allowed and disallowed dates are visibly distinguished across month boundaries without changing date selection behavior.
Written by the indexing model from the issue text.
Description
- Nextcloud-Version: 33.0.5.1 (Docker)
- Forms-Version: 5.4.0
Problem:
When answering a form containing a date picker with a start- and/or end-date range, it mostly has to be communicated in the question/description. This can sometimes be some hassle for the user, especially if the range cannot be displayed within the same month.
Suggestion:
I would suggest adding a client-side visualization adjustment of the datepicker, where the allowed and not allowed dates, if given, are colored accordingly.
Additional Thoughts:
Implementation should be without major changes, as the user already receives the start/end detail of the question by default when loading the form. Furthermore, with the new change that these ranges are saved as a Datestring instead of a Unix timestamp, this might further simplify this implementation (assuming older Forms, which are still using Unix timestamps, are not supposed to get this QoL improvement).
Two example mockup images of how it could look (the valid time range is, in this example, 18.08-22.08):
- Dominant language
- JavaScript
- Stars
- 382
- Forks
- 127
- Avg merge
- 19h 31m
- Merged PRs (30d)
- 75
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.
More from nextcloud/forms
-
[Bug]: Forms: `"CustomMessage":"The filename fallback must only contain ASCII characters."}` error Open1. to develop bug upstream
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
1. to develop bug pending fix regression
Difficulty 3/5 1-2 days Newbie friendliness 65/100
-
1. to develop enhancement feature: 📑 form creation good first issue javascript
nextcloud/forms#3587 · 2 comments · 1 reaction · 1 assignee ·
-
1. to develop bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
1. to develop enhancement feature: 📝 submitting responses technical debt
Difficulty 3/5 1-2 days Newbie friendliness 58/100
Similar issues
-
curation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
amponce/archive-movie-browser#186 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
clerk/javascript#9852 ·
-
bug p1 tools
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
factory-active factory-automatic task-bug-reproduction-cannot-reproduce task-identify-harness-labels-done task-identify-issue-type-done
Difficulty 2/5 1-3 hours Newbie friendliness 84/100