Give the Settings and History screens a Dependencies record #183
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
ethan-hann/SavePoint#183
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
.agents/coding-standards/app-mvvm-view-models.mdsays a screen factory gets only what the screen needs, in a<Screen>Dependenciesrecord, and never keeps the wholeFeatureContext.SettingsScreenFactoryandHistoryScreenFactoryboth keepFeatureContextand readServicesfrom it. Build aSettingsDependenciesand aHistoryDependenciesinFeatureComposition.Settings.csandFeatureComposition.History.cs, asActivityDependenciesdoes.Shipped in 0.9.17 (PR 227).