Tree: de47829dc2

adjust-note

button-visual-enhancement

bvc-shortcut

claim-view-improvements

cleanup-and-qr-code

contact-amounts-ui-improvements

design-tweaks-2023-12

experimental_plugin

feat/vitejs

fix-contact-totals

friend-tech-inspired-pwa-dialog

gifted-camera-improvements

home-infinite

home-view-notification-improvements

identity-switcher

increment-derived

jdenticon-entity-photos

many-misc

master

misc2

miscellany

more-smalls

move-id-switch

new-web-push

no-accounts-in-memory

notification-request-permission-dialog

notiwind-alert

openssl

photo-ratio

photo-upload

plan-loc

polish-ui-project-view

project-gives

project-map-link

projects-view-improvements

qr-reader

qr-reader-rebased

quicknav-component

remove-old-alerts

search-bbox

searching

seed-backup-view-improvements

service-worker-final

similarify-search

simple-signer

starred-projects

sw-cleanup

tmp

try-cypress

tweaks

ui-fix

update-api-server

vite-version

web-push-permissions

why-migrate-fail

world-fix

yml-fixes

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

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from 'de47829dc2'

${ noResults }

Commit Graph

1 Commits (de47829dc243d558724dacab6ac4781abba072b6)

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	1 month 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	2 months 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	2 months ago