Add autocomplete to project collection logic tag dropdown #1198
Conversation
This file contains hidden or 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
- Added autocomplete to collection project logic's tag dropdown to make it consistent as existing tags dropdown Contributes to: DependencyTrack#1147 Signed-off-by: Ja Young Lee <43683780+jayolee@users.noreply.github.com>
290a78b to
caa50d6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
Added autocomplete to Project Collection Logic's tags dropdown to make the UX consistent as "Tags" dropdown within the same modal.
Addressed Issue
Closes: #1147
Additional Details
searchTagsmethod to receive the input string as a parameter so the method can be used for both collection tag and project tag.tagsAutoCompleteItemsfor autocomplete list since only one dropdown can be focused at a time.Autocomplete screenshot:
Checklist
This PR introduces new or alters existing behavior, and I have updated the documentation accordingly