We should memoize the callback

Instead of focusing on the implementation detail that we use thread id, the name should focus on the difference in behavior. So it this case it should tell whether we're going to stay on the page or open something else.

We have duplicated logic here. Can we refactor it so that there's just one dispatch?

Could you explain why setting empty string here works correctly?

Ok, that makes a lot of sense. We could consider determining this thread here, but it's better to let reducer figure it out.

It would be a lot safer to use null instead of empty string, though.

Can we create a callback that calls onClick conditionally and could be used here? From performance point of view it shouldn't matter, but it would be more readable to have this logic in a callback instead of setting the prop conditionally here.

In the most recent solution we use newThreadID only in chat-message-list-container so maybe we should revert moving it and keep it in chat-message-list-container.

Can we use a useCallback here? Using memo when we have a function might be confusing. On the other hand, memo is a little more performant in this case... but still, I would prefer readability here.

Nit: can we use American English instead of British English? "Behavior" instead of "behaviour"

1. "Renew" is confusing here... let's say reset-active-thread instead
2. It appears that the reset will not occur if the active thread is not pending. How about reset-active-thread-if-pending?

This too should've been a separate diff. It took a second for me to realize why it was necessary... it would've been helpful to have a separate diff name / diff description to explain why this change is necessary

At this point you can feel free to leave it in

conditionalClick is not a very helpful name. How about selectItemIfNotActiveCreation

These changes appear to have nothing to do with this diff. They should've been a separate diff, but at this point I won't object to leaving them here