Skip to content

Fix Missing Module Import Errors #236

@DrunkOnJava

Description

@DrunkOnJava

Issue Description

Multiple files are failing to compile due to missing module imports. The compiler cannot find the specified modules, preventing successful builds.

Affected Files and Missing Modules

  • App-Main/Sources/AppMain/AppContainer.swift - Missing ServicesSearch
  • Features-Analytics/Sources/FeaturesAnalytics/Views/AnalyticsHomeView.swift - Missing UIComponents
  • Features-Locations/Sources/FeaturesLocations/Views/LocationsHomeView.swift - Missing UIComponents
  • Features-Scanner/Sources/FeaturesScanner/FeaturesScanner.swift - Missing ServicesExternal
  • Services-Authentication/Sources/ServicesAuthentication/AuthenticationService.swift - Missing InfrastructureSecurity
  • Services-Business/Sources/Services-Business/Budget/BudgetService.swift - Missing InfrastructureStorage
  • Services-Search/Sources/ServicesSearch/SearchService.swift - Missing InfrastructureStorage
  • Features-Receipts/Sources/FeaturesReceipts/FeaturesReceipts.swift - Missing ServicesExternal
  • Features-Settings/Sources/FeaturesSettings/Extensions/MissingComponents.swift - Missing UIComponents
  • Features-Inventory/Sources/FeaturesInventory/ViewModels/ItemsListViewModel.swift - Missing ServicesSearch
  • UI-Core/Sources/UICore/ViewModels/BaseViewModel.swift - Missing InfrastructureNetwork
  • Infrastructure-Security/Sources/Infrastructure-Security/Authentication/CertificatePinning.swift - Missing InfrastructureStorage
  • Supporting Files/App.swift - Missing HomeInventoryApp
  • Multiple UIComponents files - Missing Foundation_Models (should be FoundationModels)

Root Cause

The primary causes are:

  1. Missing module dependencies in Package.swift files
  2. Incorrect module naming (e.g., Foundation_Models vs FoundationModels)
  3. Package target configuration issues

Solution Plan

  1. Verify and update all Package.swift files to include missing dependencies
  2. Correct module naming inconsistencies
  3. Ensure proper product name mappings in target dependencies
  4. Validate Xcode project target dependencies

Priority

High - These are foundational errors that prevent the entire project from building.

Acceptance Criteria

  • All No such module compilation errors are resolved
  • All Package.swift files have correct dependencies
  • Module naming is consistent throughout the project
  • Project builds successfully without import errors

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions