[Good first issue] Update message shown when a single index is selected in search comparison tool

[noCharger]

What is the bug?

When the search button is pressed and a single search is performed, an error message appears saying "An index is required. Select an index."

How can one reproduce the bug?

1. Select index on either left or right hand side
2. Click search button

What is the expected behavior?

Three possibilities:

1. If a single search is not permitted, display an error message but do not execute the search.
2. If a single search is permitted, delete the error message.
3. If a single search is permitted, change the font color to black and display a recommendation wording such as "try comparing search results by selecting an index."

Do you have any additional context?

I would want to clarify the expected behavior.

[noCharger]

@kgcreative @lauralexis would appreciate input on this. Thanks!

[msfroh]

One possibility (maybe silly) would be to set the second index to match the first index by default (i.e. when you select the first index, if the second index is unset, then set the second index to match the first index). Of course, you would still need to handle the case where the user explicitly unselects an index.

IMO, the "standard" use of search comparison is running functionally "similar" queries on the same index to see what changes.

[lauralexis]

A single search is permitted. A single search can be executed on either side (query 1 or query 2). I don't think the error message is necessarily a bug, because it explains why the search wasn't executed. We could adjust the error message for both sides for more clarity to say "An index is required to compare search results. Select an index." Let me know what you think.

[macohen]

I'd like to keep this as simple as we can right now. I think making the messaging clearer can work just fine, but if someone is willing to pick up @msfroh's suggestion later and that works for the UX then we could do that as well.

IMO, updating the text can work to be clearer. If we go down that path, we should also label this "good first issue."

[noCharger]

Thanks all for the great suggestions! To summarize, the next step in resolving this problem is to modify the error message. If someone wants to tweak the UX of this to auto-fill the index, please open a new issue.

[evankielley]

Will this issue be fixed by #267? If not, I can make a PR for this

[noCharger]

Will this issue be fixed by #267? If not, I can make a PR for this

Nope it's an seperate issue. Please feel free to take it!