<BsDropdown> should use defaultValue if @htmlTag is undefined #1365
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
AntonStaravoitau
approved these changes
Dec 14, 2020
simonihmig
changed the title
simonihmig
approved these changes
Dec 15, 2020
simonihmig
deleted the
dropdown-property-html-tag-misses-default-value-decorator
branch
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.
Due to missing
@defaultValuedecorator<BsDropdown>was not using default value if@htmlTag={{undefined}}.I don't think this requires test coverage. It is very unlikely to have a regression as soon as the component is refactored to
@glimmer/component.