Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[datetime] fix(DateRangePicker): use timePickerProps.defaultValue correctly #5940

Closed
wants to merge 4 commits into from

Conversation

adidahiya
Copy link
Contributor

Fixes #5825

Checklist

  • Includes tests
  • Update documentation

Changes proposed in this pull request:

Fix DateRangePicker state change handlers to account for timePickerProps.defaultValue, both in the calendar hover interactions and the updated value returned in the onChange callback.

Reviewers should focus on:

Consider addressing #5859 in this same PR...

Screenshot

2023-02-13 12 03 48

@adidahiya
Copy link
Contributor Author

Right now there is a bug with the current implementation in this PR. manually-selected times are not being respected in the state change handlers:

2023-02-13 12 07 25

@adidahiya
Copy link
Contributor Author

Add demo to docs

Build artifact links for this commit: documentation | landing | table | demo

This is an automated comment from the deploy-preview CircleCI job.

@adidahiya
Copy link
Contributor Author

use state.time as source of truth

Build artifact links for this commit: documentation | landing | table | demo

This is an automated comment from the deploy-preview CircleCI job.

@adidahiya
Copy link
Contributor Author

Closing as stale, this work needs to be re-started on the "V3" components in @blueprintjs/datetime2.

@adidahiya adidahiya closed this Oct 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

DateRangeInput2: timePickerProps defaultValue is ignored
1 participant