feat(date picker): add date picker component #124
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
change behaviour of number input: now adding seperate dates instead of having all dates be the same in all search bars
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
General Summary
Motivation and Context
Some Projects need a date Picker component. The CQL-Translator needs to handle the formatting.
So far with only one active search bar, the number input is connected to the chip.
That means, no multiple dates can be used across search bars.
Now the number ranges are put into the search bar individually so multiple number ranges can be selected in one chip and across search bars.
How Has This Been Tested?
Browsers: Chrome, Firefox, Edge, Safari
Screenshots (if appropriate):