-
Notifications
You must be signed in to change notification settings - Fork 9
feat(RelativeRangeDatePicker): remove dates hint #75
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
Conversation
|
Preview is ready. |
|
@ValeraS I suggest to remove it for now due to it buggy behaviour. What do you think about it? |
| /** A placeholder date that controls the default values of each segment when the user first interacts with them. Defaults to today's date at midnight. */ | ||
| placeholderValue?: DateTime; | ||
| /** Show dates hint on calendar button hover **/ | ||
| withDatesHint?: boolean; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think, the prop should hide the hint for better backward compatibility and it name should be "hideDatesHint".
And if we specify property "hideDatesHint" in the component, then the hint will be hidden, if not, or it is false, then the hint will be shown. Such behaviour is more logical for me
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The thing is the component accepts all the boolean properties with show prefix
Also, by default the hint will be shown, this guarantees backward compatibility, because the condition is withDatesHint !== false, not withDatesHint
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But yes, hideDatesHint looks more logical.
985b5db to
7b7c297
Compare
Closes #74