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

[datetime2] feat: DateRangeInput2 component #5390

Merged
merged 14 commits into from
Jul 11, 2022
Merged

Conversation

adidahiya
Copy link
Contributor

  • New DateRangeInput2 component uses Popover2 instead of Popover. It does not have built-in TimezoneSelect support yet.
  • DateRangeInput is now deprecated.

@blueprint-bot
Copy link

deprecate DateRangeInput

Previews: documentation | landing | table | demo

@blueprint-bot
Copy link

actually export & use DRP2

Previews: documentation | landing | table | demo

@blueprint-bot
Copy link

fix test coverage

Previews: documentation | landing | table | demo

@adidahiya

This comment was marked as outdated.

@blueprint-bot
Copy link

fix test suite

Previews: documentation | landing | table | demo

@blueprint-bot
Copy link

remove describe.only

Previews: documentation | landing | table | demo

@blueprint-bot
Copy link

update test with new helper fn semantics

Previews: documentation | landing | table | demo

@adidahiya
Copy link
Contributor Author

There are some styling issues with the time picker inside the DateRangePicker, but those are unrelated and will be addressed in a separate PR.

@adidahiya adidahiya merged commit 90b51cf into develop Jul 11, 2022
@adidahiya adidahiya deleted the ad/date-range-input2 branch July 11, 2022 19:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants