Currently ContactDetails takes contact store and profile store to uniformly provide details for contacts, from the model and own profile. It means that components accessing contacts via ContactDetails become dependent on those two stores. However in some cases it's not necessary, and lighter container for contact details would be useful (e.g. preview of own profile).
The idea is to split ContactDetails into 3 elements:
adaptor adding own profile to arbitrary contacts model
wrapper over ModelEntry customized for contact details
lightweight pod componet, aggregating contact details properties
Description
Currently
ContactDetailstakes contact store and profile store to uniformly provide details for contacts, from the model and own profile. It means that components accessing contacts viaContactDetailsbecome dependent on those two stores. However in some cases it's not necessary, and lighter container for contact details would be useful (e.g. preview of own profile).The idea is to split
ContactDetailsinto 3 elements:ModelEntrycustomized for contact details