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

Overview

Understand any codebase

At a glance

Analyzed 7 days ago.

Checking for a newer commit in the background — reload in a moment to see updated results, or use Re-analyze above to check right now.

Start Here

  1. 1

    /src/components/lore-shell (opens in a new tab)— Primary structural area: 'src/components/lore-shell'

    Inferred

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

    • [Inferred] 27 source file(s) discovered under 'src/components/lore-shell', grouped as a conservative structural fallback since no declared workspace, package, or source-root boundary was found.
  2. 2

    /src/lib (opens in a new tab)— Primary structural area: 'src/lib'

    Inferred

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

    • [Inferred] 23 source file(s) discovered under 'src/lib', grouped as a conservative structural fallback since no declared workspace, package, or source-root boundary was found.
  3. 3

    /src/analysis/js-ts (opens in a new tab)— Primary structural area: 'src/analysis/js-ts'

    Inferred

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

    • [Inferred] 20 source file(s) discovered under 'src/analysis/js-ts', grouped as a conservative structural fallback since no declared workspace, package, or source-root boundary was found.
  4. 4

    /src/components/ui (opens in a new tab)— Primary structural area: 'src/components/ui'

    Inferred

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

    • [Inferred] 16 source file(s) discovered under 'src/components/ui', grouped as a conservative structural fallback since no declared workspace, package, or source-root boundary was found.
  5. 5

    /src/analysis/python (opens in a new tab)— Primary structural area: 'src/analysis/python'

    Inferred

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

    • [Inferred] 13 source file(s) discovered under 'src/analysis/python', grouped as a conservative structural fallback since no declared workspace, package, or source-root boundary was found.
  6. 6

    /scripts (opens in a new tab)— Primary structural area: 'scripts'

    Inferred

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

    • [Inferred] 12 source file(s) discovered under 'scripts', grouped as a conservative structural fallback since no declared workspace, package, or source-root boundary was found.
  7. 7

    /e2e/at-a-glance.spec.ts (opens in a new tab)— Test for 'src/lore/at-a-glance.ts'

    Inferred

    Test file 'e2e/at-a-glance.spec.ts' matches the naming convention for 'src/lore/at-a-glance.ts'.

    • [Inferred] Test file 'e2e/at-a-glance.spec.ts' matches the naming convention for 'src/lore/at-a-glance.ts'.

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
Tests
11

/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
Tests
21

/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
Tests
5

/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
Tests
4

/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
Tests
0

/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
Tests
4

How Areas Connect

Not connected to other areas:

  • Implementation area
  • Presentational React components
View full architecture

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.