Feature: enabled/disabled state #55
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
|
Hey @KabaDH Thanks much for the contribution. 😊 |
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.
This PR is a preview and is not yet ready for production.
This PR introduces a new parameter "enabled" for all CustomDropdown constructors. Setting this parameter to "false" you set the "disabled" state. In the disabled state you can not open the dropdown. Disabled state has its own decoration (disabledDecoration). Disabled state is safe to use with empty input options data.
As a minor feature, this PR introduces parameter "closeDropDownOnClearFilterSearch". Setting this parameter to "true" will cause to close the dropdown upon clicking "Clear filter" cross in any CustomDropdown constructor with search filter.