palantir/blueprint

Unable to select a single day when the intended day equals the start or the end of a previously selected date range

Open

#3,720 opened on Sep 2, 2019

View on GitHub
 (1 comment) (0 reactions) (0 assignees)TypeScript (2,167 forks)batch import
P3Package: datetimeType: enhancementhelp wanted

Repository metrics

Stars
 (20,263 stars)
PR merge metrics
 (Avg merge 43d 10h) (27 merged PRs in 30d)

Description

Environment

  • Package version(s): 3.11.0
  • Browser and OS versions: Google Chrome 76 on macOS 10.14.5

Sandbox: https://codesandbox.io/s/blueprint-sandbox-wsj6f

Steps to reproduce

  1. Select a date range, e.g. from the 3rd of August to the 15th of August.
  2. Now you want to select the 3rd of August as a single-day range.
  3. When clicking on this day, you are unable to select it since it is already the start of the previously selected date range.
  4. The same applies if you want to use the last day of the previously selected date range, the 15th of August.

Actual behavior

When clicking the days in 3. and 4. the buttons are deselected.

Expected behavior

When clicking the days in 3. and 4. the buttons keep selected and can be used for a new single-day range.

Contributor guide

Research direction
Investigate the selection logic in the DateRangePicker component. Focus on how the component handles clicking a day that is already the start or end of a selected range. The bug occurs because the component deselects the day instead of allowing it to become a single day range. Study the state management for day selection and modify the logic to permit re selection of boundary days.
Tech stack
typescriptreact
Domain
frontend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75