fix(autocomplete): handle null and undefined values #2814
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
chirichok98
changed the title
yggg
suggested changes
Aug 6, 2021
src/framework/theme/components/autocomplete/autocomplete.directive.ts
Outdated
Show resolved
Hide resolved
Co-authored-by: Sergey Andrievskiy <yggg@users.noreply.github.com>
yggg
approved these changes
Aug 25, 2021
yggg
changed the title
yggg
changed the title
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.
Please read and mark the following check list before creating a pull request:
Short description of what this resolves:
Fixes #2352
Before fix:
Autocomplete ignores null and undefined values.
After fix:
Autocomplete sets empty string as displayValue for input and sets null and undefined as value of control.