Skip to content

modularization folders architecture  #109

@amine2233

Description

@amine2233

tank you for your awesome work

i have a question about architecture all the folders and sub-folders, in modularization project.

what is the differences between this two approaches ?

first approach

we put each modules in separated module like bellow

|- Module-1
  |- Package.swift
  |- Source
    |- Module-1
  |- Tests
    |- Module-1-Tests
|- Module-2
  |- Package.swift
  |- Source
    |- Module-2
  |- Tests
    |- Module-3-Tests
|- Module-3
  |- Package.swift
  |- Source
    |- Module-3
  |- Tests
    |- Module-3-Tests
|- Module-4
  |- Package.swift
  |- Source
    |- Module-4
  |- Tests
    |- Module-4-Tests

we put each modules in one Root module like bellow

|- RootModule
  |- Package.swift
  |- Source
    |- Module-1
    |- Module-2
    |- Module-3
    |- Module-4
  |- Tests
    |- Module-1-Tests
    |- Module-3-Tests
    |- Module-3-Tests
    |- Module-4-Tests

Whats is Pro and Cons between this two approaches

Xcode issue ? when importing the modules ?
Conflict Dependencies if each module use same dependency example (Module1 & Module3) use same dependency (Alamofire) ?
Maintain ?
TimeBuild ?
Git ?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions