You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
micieslak
changed the title
Decompose ContactDetails into modular subcomponents
Decompose ContactDetails into smaller, flexible components
Nov 21, 2024
Description
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 viaContactDetails
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:ModelEntry
customized for contact detailsThe text was updated successfully, but these errors were encountered: