palantir/blueprint

[DateRangePicker] [DateRangeInput] Allow min/max bounds to be removed

Open

#877 opened on Mar 22, 2017

View on GitHub
 (10 comments) (4 reactions) (0 assignees)TypeScript (20,263 stars) (2,167 forks)batch import
P2Package: datetimeStatus: work in progressType: enhancementhelp wanted

Description

Is it possible to remove min / max dates on date-related inputs? There are times when any date is valid and that's just currently not possible.

  • Package version(s): Datetime 1.9.1

Contributor guide

Tech stack
typescriptreact
Domain
frontend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
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.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
ReactBlueprint component libraryTypeScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Investigate the current implementation of DateRangePicker and DateRangeInput in the Blueprint component library, specifically how min/max bounds are enforced. Determine how to allow removing these bounds by accepting undefined or null values for min/max props. Review the component's source code in the datetime package (e.g., src/dateRangePicker.tsx) and any related documentation. Consider backward compatibility and potential breaking changes.
[DateRangePicker] [DateRangeInput] Allow min/max bounds to be removed · palantir/blueprint#877 | Good First Issue