ContactDetails decomposed into smaller, more specialized components #16794
+475
−877
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does the PR do
Decomposes original
ContactDetails
into more specialized components that can be used together or separately, depending on the needs/context:ContactDetails
- plain container for data (to aggregate all contact details properties into single entity)AllContactsAdaptor
- adaptor which allows to addself
contact to arbitrary model of contactsContactModelEntry
- wrapsModelEntry
to expose contact entry in a convenient, type-safe wayMoreover:
ProfileDialogView
simplification - no need to handle dirty values in a special way,dirty
/dirtyValues
properties removedProfileDialogView
takes only contact details, caller can decide how to provide itCloses: #16793
Depends on: #16667
Affected areas
mainly:
ContactDetails
,ProfileDialogView
Architecture compliance
My PR is consistent with this document: Status Desktop Architecture Guide