v1.5.1: Remove Profiles and Semantic Search - #1
Merged
Conversation
DELETED FILES: - Sources/SmartFileSorter/Models/ProfileManager.swift - Sources/SmartFileSorter/Models/SemanticSearchEngine.swift - Sources/SmartFileSorter/Views/SemanticSearchView.swift MODIFIED FILES: - App.swift: removed ProfileManager.shared init - MainView.swift: removed profile picker section + semantic nav link + route - MenuBarView.swift: removed profile picker + profileManager property - WatcherViewModel.swift: removed ProfileManager subscription + Combine import - RuleEngine.swift: removed currentProfile computed property, hardcoded 'Home' - FSEventsWatcher.swift: hardcoded activeProfile='Home', cleaned log messages - ScheduleManager.swift: hardcoded activeProfile='Home' - SorterEngine.swift: hardcoded activeProfile='Home' - HistoryManager.swift: hardcoded activeProfile='Home', added DROP TABLE migration - OnboardingView.swift: renamed createInitialProfile -> createInitialRule - CHANGELOG.md: added v1.5.1 entry - Tests/SorterEngineTests.swift: profileName='TestProfile' -> nil NLContextualEmbedding DECISION: REMOVED (0 callsites found in entire codebase) MIGRATION: - profiles.json on disk: silently ignored (never read) - embeddings SQLite table: DROP TABLE IF EXISTS in HistoryManager migration - watcher_paths_Home key: continues working (backward compatible) - BatchRecord.profileName field: KEPT for data compatibility
- RuleEngine.rulesFileURL now points to 'rules.json' - On launch, if rules_Home.json exists but rules.json does not, FileManager.moveItem migrates the file and logs once
Removed from 8 files: - FSEventsWatcher: activeProfile → direct 'watcher_paths' key + migration - ScheduleManager: activeProfile → direct 'watcher_paths' key - SorterEngine: removed activeProfile + profileName from 2 batch sites - WatcherViewModel: removed profileName from batch creation - HistoryManager: removed BatchRecord.profileName field, SQLite column, INSERT/SELECT queries updated, ALTER TABLE DROP COLUMN migration added - DashboardView: removed profile column from CSV export - SorterEngineTests: removed profileName argument Migration additions: - FSEventsWatcher: watcher_paths_Home → watcher_paths (copy + remove old) - HistoryManager: ALTER TABLE batches DROP COLUMN profile_name (SQLite 3.35+) Grep evidence: - activeProfile|currentProfile: 0 results - ProfileManager: 0 results - 'profile' in Sources: only migration code (DROP COLUMN, legacy key refs) - '_Home' in Sources: only migration code (rules_Home.json, watcher_paths_Home)
CHANGELOG v1.5.1: - Added ### Changed section (rules.json rename, watcher_paths rename, CSV) - Updated ### Removed to include BatchRecord.profileName - Updated ### Notes to reflect migration-only references Design spec updated with: - Revised acceptance criteria (stricter) - Migration table - Exception list for grep results
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Pure cleanup PR — removes Profile system and Semantic Search entirely from the codebase. No new features, no visual changes.
Deleted Files (3)
Sources/SmartFileSorter/Models/ProfileManager.swiftSources/SmartFileSorter/Models/SemanticSearchEngine.swiftSources/SmartFileSorter/Views/SemanticSearchView.swiftModified Files (14)
App.swiftProfileManager.sharedinitMainView.swiftMenuBarView.swift@ObservedObjectWatcherViewModel.swiftprofileNamefrom batchRuleEngine.swiftcurrentProfile, renamedrules_Home.json→rules.json+ migrationFSEventsWatcher.swiftactiveProfile,watcher_pathskey + migration from legacy_HomeScheduleManager.swiftactiveProfile, directwatcher_pathskeySorterEngine.swiftactiveProfile+profileNamefrom 2 batch sitesHistoryManager.swiftBatchRecord.profileName,profile_namecolumn, DROP COLUMN migrationDashboardView.swiftOnboardingView.swiftcreateInitialProfile()→createInitialRule()CHANGELOG.mdSorterEngineTests.swiftprofileNameargumentdocs/specs/...NLContextualEmbedding Decision
REMOVED — 0 callsites found. SemanticSearchEngine was the only consumer; file deleted entirely.
Migrations (run on first launch after upgrade)
rules_Home.jsonmoveItem→rules.jsonwatcher_paths_HomeUD keywatcher_paths, remove old keyprofile_nameSQLite columnALTER TABLE DROP COLUMNembeddingsSQLite tableDROP TABLE IF EXISTSprofiles.jsonon diskReview Feedback Addressed (Round 2)
What changed
rules_Home.json→rules.json— RuleEngine now usesrules.jsonwith migration from legacy namewatcher_paths_Home→watcher_paths— FSEventsWatcher migrates on restore, removes old keyactiveProfileeliminated — removed from FSEventsWatcher, ScheduleManager, SorterEngine, HistoryManager (was hardcoded to "Home")BatchRecord.profileNamedeleted — field, init param, CodingKeys, decoder, SQLite column, INSERT/SELECT queries, CSV export columnprofileName: nil→ argument removed entirelyGrep Evidence
Stats
swift build