The User type was introduced in https://phab.comm.dev/D10928. Didn't show up on stack because I didn't put depends on D11001 on https://phab.comm.dev/D11049. Should be all fixed

Thanks! How about these questions?

Is this type used anywhere else? Should it be deleted?

I can't delete the type as the SearchResult I receive from my websocket server is composed of the User type. I need to keep it to properly authenticate the SearchResponse type I receive from the websocket server. It is also used in https://phab.comm.dev/D11000 for defining Promise types

If you're referring to utilizing GlobalUserInfo instead of User for defining websocket responses, that's definitely an option; however, GlobalUserInfo includes an avatar field which isn't included as part of my search index. I could return null in this case, but I use User to refer to what is currently stored per User in the search index

The avatar field is optional in GlobalAccountUserInfo

I think it's fine to define a new type if you want, but looking at it now, User is way too generic a name. Can you pick a better name, such as IdentitySearchUser?

This feedback still needs to be addressed. User is way too generic of a name for a type that is exported. Can you please rename to something like IdentitySearchUser?

Addressed Rust implementation in https://phab.comm.dev/D11096 and in JavaScript in latest revision of https://phab.comm.dev/D10928