Static Dependencies* · guardian/facia-scala-client

Logical Decomposition #1: PRIMARY

The decompositions is based on the folder structure at level 1 (relative to the source code root).

Static Dependencies

Dependencies among components are static code dependencies among files in different components.

Analyzed system has 2 links (arrows) between components.
The number on the arrow represents the number of files from referring component that depend on files in referred component.
These 2 links contain 8 dependencies.

flowchart TB
    n0["fapi-client"]
    n1["cdk"]
    n2["fapi-client-core"]
    n3["project"]
    n4["facia-json"]
    n0 -->|"6"| n4
    n0 -->|"2"| n2
    classDef default fill:#808080,stroke:#ffffff,color:#000000;
    classDef highlighted fill:#00b2ee,stroke:#ffffff,color:#000000;
    class n0,n1,n2,n3,n4 highlighted;
    linkStyle 0 stroke:#00688bB7,stroke-width:6px
    linkStyle 1 stroke:#00688b70,stroke-width:2px

Download: Mermaid (.mmd) (open online Mermaid editor)

Explore: 2D force graph | 3D force graph

Show more details about dependencies...

From Component --> To Component	From Component (files with dependencies)	Details
fapi-client --> facia-json	fapi-client/src/main/scala/com/gu/facia/api/FAPI.scala fapi-client/src/main/scala/com/gu/facia/api/CustomSubnavService.scala fapi-client/src/main/scala/com/gu/facia/api/utils/ContainerBrandingFinder.scala fapi-client/src/main/scala/com/gu/facia/api/utils/ResolvedMetaData.scala fapi-client/src/main/scala/com/gu/facia/api/utils/ItemKicker.scala fapi-client/src/main/scala/com/gu/facia/api/utils/Backfill.scala	6 source files
fapi-client --> fapi-client-core	fapi-client/src/main/scala/com/gu/facia/api/FAPI.scala fapi-client/src/main/scala/com/gu/facia/api/utils/Backfill.scala	2 source files

About This Analysis

Static code dependencies refer to the relationships between different modules, libraries, or components in a software system that are established at compile-time rather than at runtime. These dependencies are determined by the code itself, meaning that one module directly references another through imports, includes, or explicit references in the code. Examples include:

Library and Module Imports
Class Dependencies (Inheritance & Composition)
Function and Method Calls
Dependency Injection Without Runtime Resolution

Learn more...

To learn more about good practices on componentization and dependencies, Sokrates recommends the following resources:

Reduce Coupling, MartinFlower.com (IEEE Software article)
Couplers Code Smells, sourcemaking.com

2026-10-07 12:30