Skip to main content
nielse63/RepoLorePublic
Analysis currentAnalyzed 7 days agodevtypescript

Architecture

How the major parts of this repository work together.

RepoLore

Languages
typescript
Frameworks
react

Major Areas

Ordered by detected direct relationships (depends on + imported by), then entry points, then name; tests and tooling configuration are listed last.

  • /src/lore (opens in a new tab)

    Groups 11 source file(s) under 'src/lore'; no declared workspace, package, or source-root boundary was found, so files are grouped by directory.

    Entry points
    0
    Depends on
    1
    Imported By
    18
    Evidence
    1
  • /src/lib (opens in a new tab)

    Groups 23 source file(s) under 'src/lib'; no declared workspace, package, or source-root boundary was found, so files are grouped by directory.

    Entry points
    0
    Depends on
    3
    Imported By
    15
    Evidence
    1
  • /src/analysis (opens in a new tab)

    Groups 5 source file(s) under 'src/analysis'; no declared workspace, package, or source-root boundary was found, so files are grouped by directory.

    Entry points
    0
    Depends on
    11
    Imported By
    5
    Evidence
    1
  • /src/db (opens in a new tab)

    Groups 8 source file(s) under 'src/db'; no declared workspace, package, or source-root boundary was found, so files are grouped by directory.

    Entry points
    0
    Depends on
    3
    Imported By
    12
    Evidence
    1
  • /scripts (opens in a new tab)

    Groups 12 source file(s) under 'scripts'; no declared workspace, package, or source-root boundary was found, so files are grouped by directory.

    Entry points
    0
    Depends on
    12
    Imported By
    0
    Evidence
    1
  • /src/github (opens in a new tab)

    Groups 8 source file(s) under 'src/github'; no declared workspace, package, or source-root boundary was found, so files are grouped by directory.

    Entry points
    0
    Depends on
    1
    Imported By
    10
    Evidence
    1

Component Connections

Not connected to other areas:

  • Implementation area
  • Presentational React components

Entry Points

Gaps

  • UnknownNo relative import or naming convention identifies a single implementation file for 'e2e/accessibility.spec.ts' — expected for a page/flow-level e2e spec, which doesn't test one importable module the way a unit test does.
  • UnknownNo relative import or naming convention identifies a single implementation file for 'e2e/area-dependency-diagram.spec.ts' — expected for a page/flow-level e2e spec, which doesn't test one importable module the way a unit test does.
  • UnknownNo relative import or naming convention identifies a single implementation file for 'e2e/area-relationships-pagination.spec.ts' — expected for a page/flow-level e2e spec, which doesn't test one importable module the way a unit test does.
  • UnknownNo relative import or naming convention identifies a single implementation file for 'e2e/coverage.ts' — expected for a page/flow-level e2e spec, which doesn't test one importable module the way a unit test does.
  • UnknownNo relative import or naming convention identifies a single implementation file for 'e2e/data-flow-default.spec.ts' — expected for a page/flow-level e2e spec, which doesn't test one importable module the way a unit test does.
  • UnknownNo relative import or naming convention identifies a single implementation file for 'e2e/history-dependencies.spec.ts' — expected for a page/flow-level e2e spec, which doesn't test one importable module the way a unit test does.
  • UnknownNo relative import or naming convention identifies a single implementation file for 'e2e/home.spec.ts' — expected for a page/flow-level e2e spec, which doesn't test one importable module the way a unit test does.
  • UnknownNo relative import or naming convention identifies a single implementation file for 'e2e/major-areas-order.spec.ts' — expected for a page/flow-level e2e spec, which doesn't test one importable module the way a unit test does.
  • UnknownNo relative import or naming convention identifies a single implementation file for 'e2e/major-areas-pagination.spec.ts' — expected for a page/flow-level e2e spec, which doesn't test one importable module the way a unit test does.
  • UnknownNo relative import or naming convention identifies a single implementation file for 'e2e/marketing.spec.ts' — expected for a page/flow-level e2e spec, which doesn't test one importable module the way a unit test does.
  • UnknownNo relative import or naming convention identifies a single implementation file for 'e2e/mobile-responsive.spec.ts' — expected for a page/flow-level e2e spec, which doesn't test one importable module the way a unit test does.
  • UnknownNo relative import or naming convention identifies a single implementation file for 'e2e/nested-test-samples.spec.ts' — expected for a page/flow-level e2e spec, which doesn't test one importable module the way a unit test does.
  • UnknownNo relative import or naming convention identifies a single implementation file for 'e2e/repo-spelling-redirect.spec.ts' — expected for a page/flow-level e2e spec, which doesn't test one importable module the way a unit test does.
  • UnknownNo relative import or naming convention identifies a single implementation file for 'e2e/right-rail.spec.ts' — expected for a page/flow-level e2e spec, which doesn't test one importable module the way a unit test does.
  • UnknownNo relative import or naming convention identifies a single implementation file for 'e2e/seo.spec.ts' — expected for a page/flow-level e2e spec, which doesn't test one importable module the way a unit test does.

Test Relationships