Tree:
fb2ac963bd
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
claim-view-error-handling
claimview-fullfills-offer
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
get-get-hash
gifting-periphery-improvements
gifting-ui-2025-05
home-icon-enhancements
home-view-notification-improvements
homeview-cleanup-2025-03
homeview-refresh-2025-02
imagemagick-anrdoid
ios-contact-copy
logger-level
logging-upgrade
main
master
master-settings-upgrade
matthew-scratch-2025-06-28
migrate-dexie-to-sqlite
nearby-filter
new-storage
nostr
notification-line-wrapping
notification-request-permission-dialog
notification-section
notify-time
offer-edit
offer-validation-logic
onboarding-dialog-fix
passkey
passkey-cache
performance-optimizations-testing
photo-reverse
plan-loc
platformservicemixin-interface-consolidation
playwright-pwa-install-test
playwright-test-60-fix
playwright-test-updates
profile-pic
project-gives
qrcode-capacitor
registration-gate
remove-image-cache
replace-iconrenderer
script-build-mode
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 }
1 Commits (fb2ac963bd61abaca7ba361cf2d4b811244ddd70)
| Author | SHA1 | Message | Date |
|---|---|---|---|
Matthew Raymer
|
db5da0cdfc |
docs: reorganize documentation structure with 7-item folder limits
- Create logical sub-folder classification for all documentation - Organize 91 migration files into component-specific folders - Separate user guides, build system, migration, and development docs - Maintain maximum 7 items per folder for easy navigation - Add comprehensive README and reorganization summary - Ensure all changes tracked in git with proper versioning Structure: - user-guides/ (3 items): user-facing documentation - build-system/ (3 items): core, platforms, automation - migration/ (6 items): assessments, testing, templates - development/ (4 items): tools and standards - architecture/, testing/, examples/ (ready for future docs) Total: 24 folders created, all within 7-item limits |
4 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 |
1 month ago |
|
Matthew Raymer
|
72041f29e1 |
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 |
1 month ago |