Parity gallery: honest populated-state coverage (10/34 surfaces differ)
Fixed & documented, not-just-marketed: - HomeScreen now derives summary card from LocalDataManager.myResidences with VM fallback — populated PNG genuinely differs from empty. - DocumentsScreen added same LocalDataManager fallback pattern + ambient subscription check (bypass SubscriptionHelper's singleton gate). - ScreenshotTests.setUp seeds the global DataManager singleton from the fixture per variant (subscription/user/residences/tasks/docs/contractors/ lookups). Unblocks screens that bypass LocalDataManager. Honest coverage after all fixes: 10/34 surface-pairs genuinely differ (home, profile, residences, contractors, all_tasks, task_templates_browser in dark mode, etc.). The other 24 remain identical because their VMs independently track state via APILayer.getXxx() calls that fail in Robolectric — VM state stays Idle/Error, so gated "populated" branches never render. Root architectural fix needed (not landed here): every VM's xxxState should mirror DataManager.xxx reactively instead of tracking API results independently. That's a ~20-VM refactor tracked as follow-up in docs/parity-gallery.md "Known limitations". Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Binary file not shown.
|
Before Width: | Height: | Size: 4.7 KiB After Width: | Height: | Size: 37 KiB |
Reference in New Issue
Block a user