Bug: Advanced Search boolean types get deselected or cannot get reselected. #474
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.
Overview
When adding multiple query options to search, when you start typing, the boolean type (
AND
,OR
,NOT
) disappears. You then cannot selectAND
. Two problems were discovered in thereducer
:state[dsUid].fieldedSearches[index].booleanTypes
does not exist, makingbooleanType
returnundefined
.booleanType ? ...
ternary operator returnsfalse
when set toAND
because thevalue
ofAND
is0
, which is also equivalent tofalse
. It now specifically checks if it is a number and is less than the number of available boolean types to prevent the use of a magic number that does not exist as a type.Anything else?
Focusing on a radio button turned the button into a square. That is because of the
:focus
pseudo-class definingborder-radius: 2px
. Addingborder-radius: 50%!important
to the radio button resolves this style bug.Testing