As an ... I want to ... in order to ...
during the usability test some participants did not select an option from the lookup menu when the option matched their search. This resulted in an invalid condition which leads to an error when running the query. Additionally, as a consequence the value field will not adapt to the property type and then later remove the input when a valid property was selected.
I'm assuming this is a more a component behavior that we need to tweak. for example immediately displaying an error state or selecting the top most match for the user.
Proceeding without selecting a valid property from the
lookup component menu means the input is not recognized and the value field doesn’t switch to the correct component.
After running the query the field indicates an error. After selecting a valid property from the menu, the value field switches to the correct component, but loses the previous input from the user.