fix(BB-793): Improve the UX with the search field option entity #1075
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.
Hi there,
While searching for issues to contribute to Bookbrainz I found
BB-793
for improving the UX of the add authors to collection form, I have found it a good start for a beginner such as me so I have started to work to know where is the problem and how to solve it.Problem
The first time, I was trying to improve the search field element in authors to collection form such as the
BB-793
issue, then I found that the search field element at more places such as add collaborators to the collection as you can see in the images below.Solution
The first solution was to add a CSS class to handle the search field width to be suitable to screen width and provide a good UX, but I have found that this has happened but no effect we can notice.
The class
Select
is responsible for handling the width of the element, but it didn't work because the cloned element took its props from the parent of the wrapper select element without taking the wrapper select props as expected.Areas of Impact
The PR effect on the common element
EntitySearchFieldOption
which is a part of the entity editor.