In security solution, we have our own error toaster component addError. When we made the switch from GraphQL to Search Strategy, we were unaware of the Search Strategy data.search.showError method and continued using addError. The showError includes special error handling for specific cases. For example, take a look at the same error passed to addError, and then passed to showError:
We should replace every addError handling an error for search strategy (data.search.search) with the data.search.showError method.
In security solution, we have our own error toaster component
addError
. When we made the switch from GraphQL to Search Strategy, we were unaware of the Search Strategydata.search.showError
method and continued usingaddError
. TheshowError
includes special error handling for specific cases. For example, take a look at the same error passed toaddError
, and then passed toshowError
:We should replace every
addError
handling an error for search strategy (data.search.search
) with thedata.search.showError
method.I have already made the change in timeline, which is the gifs above: https://github.com/elastic/kibana/pull/125178