Chat: fix at symbol title

[abeatrix]

#3530

A user on Discord has reported that Cody is incorrectly showing an error message "No symbols found (try installing language extensions and opening a file)":

This error message/tooltip is incorrect as the result is expected to be empty when the query is empty, and not required to have a file opened for symbol search, this PR reverts the tooltip back to 'Search for a symbol to include...' to display on start-up screen.

Test plan

• Type @# in the input, you should see 'Search for a symbol to include...'
• No symbols found is displayed when no result is returned after typing more than 1 character

[toolmantim]

I'd like to leave this message in if there are 2 or more chars after @# but no results. Only because sometimes the VS Code API does return results after a period of time (and there's no API for loading state).

But we can make the message:

"No symbols found. Symbols may be loading, or language extensions not installed."

(May need overflow ellipsis)

[abeatrix]

I'd like to leave this message in if there are 2 or more chars after @# but no results. Only because sometimes the VS Code API does return results after a period of time (and there's no API for loading state).

But we can make the message:

"No symbols found. Symbols may be loading, or language extensions not installed."

(May need overflow ellipsis)

I think there's a way to check if symbol providers are available in the current workspace or not to display the tooltip more accurately. Let me check on Monday to confirm, and we can add the "(symbols may be loading)" only if that works? @toolmantim

[toolmantim]

Oh amazing! That would be even better.

[abeatrix]

@toolmantim instead of "No symbols found (symbol maybe be loading)", what do you think about "Searching symbols..." and then display "No symbols found" after a timeout?

[toolmantim]

I thought the API immediately returns a nil result? But if that's not right, or you're thinking of polling/retrying… some kind of experience like that could be nice. How would you calculate the timeout though, because huge codebases could take a very long time, and I'd still want us to show "(language extensions may be loading)"

[abeatrix]

I thought the API immediately returns a nil result?
That's my understanding as well but I misunderstood you when you said "only because sometimes the VS Code API does return results after a period of time (and there's no API for loading state)", which I just realized you are referring to when the symbol provider is initiating.

Updated to

[toolmantim]

It's looking good, but I wouldn't show the "(language extensions may be loading)" above two characters, because there's a good chance there's simply no matching symbols:

Two characters and under, you can be pretty sure there should always be a result, so something went wrong.