eslint-disable-next-line no-unused-vars will be removed in next diff with functions implementation

Agree - it doesn't need to be specified
For me, it makes code more readable to explicitly define direction instead of wondering what is the default one while reading the code.
We have multiple uses of flex-direction: row; in our codebase by different authors, and I think it should also be left here.

You're absolutely right. Thanks for catching!

Thanks!

Probably not, although I prefer returning explicitly null for no-component case, because it indicates that tagsList is by purpose an empty component - and not undefined one.

It's hard to say, because we do not have design for this component in Figma. I have the feeling, that this component in native doesn't contain anywhere information that we are searching users for creating a new thread, so used the longer text here.
However, I'm not completely sure about it.
Maybe other team members will have suggestion what should be here (@palys-swm, @atul)

OK, as long as you have a rationale, that makes sense!

Makes sense

The idea is to display user suggestions list when there is empty input only when no users have been selected.
It's how it works on native.
When we start creating a thread, we immediately receive list of users, which covers the screen. However, when we select some users to a chat, we display list of suggested users only if we input some text - so it doesn't cover chat all the time:

It's redundant and I'll remove it.
It was used to change styling (user list height) so the list doesn't cover the whole view of thread (that matches selected set of users)