trent_larson/crowd-funder-for-time-pwa - crowd-funder-for-time-pwa - Gitea: Git with a cup of tea

Author	SHA1	Message	Date
Matthew Raymer	41a8e4e7a8	Fix HomeView notification migration to use proper constants pattern - Add NOTIFY_CONTACT_LOADING_ISSUE, NOTIFY_FEED_LOADING_ISSUE, and NOTIFY_CONFIRMATION_ERROR constants to notifications.ts - Update HomeView.vue to import and use notification constants instead of literal strings - Update migration templates to document constants vs literal strings pattern - Add comprehensive documentation for notification constants usage Ensures consistency with established pattern used in ActivityListItem.vue and other migrated components. Linter passes without errors.	3 weeks ago
Matthew Raymer	223e497b85	feat: enhance validation script with accurate mixed pattern detection Validation Script Enhancements: - ✅ Fix false positive detection by excluding comments from legacy pattern search - ✅ Add technically compliant files category (mixin + no legacy code) - ✅ Add human testing status tracking and reporting - ✅ Create comprehensive documentation for testing process MembersList.vue Status Resolution: - ✅ Confirmed fully migrated (was false positive due to migration comments) - ✅ Ready for human testing validation - ✅ Created comprehensive testing guide Statistics Correction: - Mixed pattern files: 6 → 3 (eliminated 50% false positives) - Technically compliant: 15 files identified - Human testing: 2 confirmed, 13 awaiting validation Documentation: Created testing tracker, analysis docs, and MembersList testing guide	3 weeks ago
Matthew Raymer	b450689702	Migrate LogView.vue to PlatformServiceMixin with architectural compliance Achieve total architectural compliance by eliminating both legacy database utilities and direct SQL queries from LogView.vue component. Component Changes (LogView.vue): - Replace databaseUtil.memoryLogs with this.$memoryLogs - Replace direct SQL query with this.$logs() abstraction - Remove PlatformServiceFactory and databaseUtil imports - Add PlatformServiceMixin to component mixins - Reduce component from database-aware to pure presentation layer Mixin Enhancements (PlatformServiceMixin.ts): - Add $memoryLogs computed property for memory logs access - Add $logs() method for abstracted database log retrieval - Update TypeScript interfaces (IPlatformServiceMixin, ComponentCustomProperties) - Enable components to access logs without SQL knowledge Documentation: - Add docs/migration-testing/TESTING_LOGVIEW.md - Quick testing guide - Add docs/migration-testing/migration-checklist-LogView.md - Comprehensive checklist - Document architectural compliance achievements and testing requirements Architectural Benefits: - Zero databaseUtil imports in LogView.vue - Zero direct SQL queries in component layer - Proper separation of concerns (View → Service → Database) - Reusable $logs() method for other components - Sets gold standard for future migrations Migration Progress: - Components using PlatformServiceMixin: 14/91 (15%) - LogView.vue achieves total architectural compliance - Reduces legacy databaseUtil imports from 52 to 51 Testing: Ready for testing at /logs route Backwards Compatible: Yes - no functional changes to end users	4 weeks ago
Matthew Raymer	73b81d2a90	fix: Remove explicit axios declaration in ClaimAddRawView - Remove conflicting axios!: AxiosStatic declaration - Let Vue's axios plugin handle injection naturally - Fix HTTP request errors in raw claim editor - Clean up unused AxiosStatic import - Verified build and lint success	4 weeks ago
Matthew Raymer	6c0142b5fd	Fix migration dates, add multi-platform testing infrastructure, and organize docs Migration Date Corrections: - Update all migration TODO comments to use correct date: 2025-07-06 - Add proper TypeScript type declarations for $route and $router in DeepLinkErrorView - Fix template property references to use $route instead of route Multi-Platform Testing Infrastructure: - Add comprehensive multi-platform testing requirements for migrations - Update component migration template with platform testing requirements - Establish sign-off requirements for web, desktop, and mobile platforms - Document expected outcomes and validation procedures Migration Testing Organization: - Create docs/migration-testing/ folder for testing documentation - Move TESTING_CONTACTIMPORT.md from project root to migration-testing/ - Relocate all migration-checklist-.md files to migration-testing/ - Add comprehensive README.md with organization guidelines - Update file references in components and TODOs - Establish naming conventions and quality standards Files added: - docs/migration-testing/README.md - docs/migration-testing/TESTING_CONTACTIMPORT.md - docs/migration-testing/migration-checklist-ContactImportView.md - docs/migration-testing/migration-checklist-MembersList.md Files modified: - src/views/ContactImportView.vue (date correction) - src/components/MembersList.vue (date correction, reference path update) - src/views/DeepLinkErrorView.vue (date correction, Vue router types) - docs/migration-templates/component-migration.md (multi-platform requirements) Files moved: - TESTING_CONTACTIMPORT.md → docs/migration-testing/ - docs/migration-checklist-.md → docs/migration-testing/ This establishes comprehensive testing infrastructure for all future migrations with proper organization and multi-platform validation requirements.	4 weeks ago