nextcloud / nextcloud/forms

QoL: Visualize Dateranges within the Datepicker

Open
#3,683 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage enhancement
Dominant language
JavaScript
Stars
382
Forks
127
Avg merge
19h 31m
Merged PRs (30d)
75

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):

Image Image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

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.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
67/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.