Tree:
41a8e4e7a8
ai-context
android-15-check
app_id_fix
ask-for-contacts-export
build-dev-to-dist
build-improvement
build-ios
build-with-env
capacitor-local-save
contact-gifting-current-user
contacts-view-fixes
cross-platform-factory
cross-platform-factory-redux
d9085ced6df7dc7bdcd899959cea6489cab7f8b8
db-backup-cross-platform
deep-link
deep-links-android-update
deep_linking
design-tweaks-2023-12
electron_fix_20250317
experimental_plugin
eye-slash
fix-contact-import-export
fix-service-worker
friend-tech-inspired-pwa-dialog
gifting-periphery-improvements
gifting-ui-2025-05
home-icon-enhancements
home-view-notification-improvements
homeview-cleanup-2025-03
homeview-refresh-2025-02
ios-contact-copy
logging-upgrade
main
master
master-settings-upgrade
matthew-scratch-2025-06-28
migrate-dexie-to-sqlite
new-storage
nostr
notification-line-wrapping
notification-request-permission-dialog
notification-section
notify-time
offer-edit
onboarding-dialog-fix
passkey
passkey-cache
photo-reverse
plan-loc
playwright-pwa-install-test
profile-pic
project-gives
qrcode-capacitor
registration-gate
replace-iconrenderer
search-map-fix
side_step
simple-signer
split_build_process
sql-absurd-sql
sql-absurd-sql-further
sql-wa-sqlite
star-projects
starred-projects
streamline-attempt
sw-cleanup
tmp
trent-tweaks
tweaks
ui-fixes-2024-03
ui-fixes-2025-03
ui-fixes-2025-06-w2
units-mocking
v-onboarding-2024-04
vite-version
web-serve-fix
web-tests
0.1.8
0.2.1
0.2.11
0.2.17
0.2.2
0.2.4
0.3.35
0.3.50
0.3.51
0.3.52
0.3.53
0.3.54
0.3.55
0.3.56
0.3.57
0.4.1
0.4.2
0.4.3
0.4.4
0.5.8
0.5.9
1.0.0
1.0.2
1.0.4
${ noResults }
3 Commits (41a8e4e7a806611394356de97e254721bcf93ad2)
| 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
|
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 |
|
Matthew Raymer
|
01bb13219f |
Add comprehensive migration documentation and testing infrastructure
- Add TODO annotation to MembersList.vue requiring human testing validation - Create migration templates for systematic component migration - Add best practices guide for PlatformServiceMixin usage - Create ESLint rules template for pattern enforcement - Add validation script to track migration progress - Document Phase 1 completion summary with current state Migration Infrastructure: - Component migration checklist template - Automated validation script (validate-migration.sh) - Best practices documentation - ESLint rules for preventing regression Status: MembersList.vue migration complete but requires human testing Next: Select next component for migration when ready to continue |
4 weeks ago |