Viewing & understanding

Project Intelligence & Impact Analysis

See how a change may spread.

Explore file relationships and what a change might affect.

01
Project analysis of the actual demonstration files.Actual Linqbase interface · demonstration project
TURN IDEAS INTO POSSIBILITIES

See how a change may spread.

Before modifying an existing project or while exploring unfamiliar code.

A file rarely stands alone. Changing a shared function can affect callers, imports and tests elsewhere. Project analysis makes supported relationships easier to investigate.

Open the project graph, select a file and inspect related nodes and source locations. Use LogicLens when you need detail within a file.

YOUR NEXT STEP

How to get started.

From your first choice to the result. Here is how to use this feature in your own project.

  1. 01

    Select the project and run the project investigation to index supported source files.

  2. 02

    Inspect relationships in the separate network window. Zoom, filter and select files to follow relevant links.

  3. 03

    Review potential impact, related sources, tests and reported uncertainties.

IN PRACTICE

How it could work for you.

Before changing a shared login helper, inspect the pages and tests that refer to it.

How to assess the result

Dynamic dependencies and unsupported languages may be missing. Confirm important impact with actual tests.

GET STARTED IN LINQBASE

Where to find it.

Top bar → Tools → Project Intelligence & Impact Analysis

Available actions depend on your plan, mode and project state. Features that require a task become available within an appropriate conversation.
SAVE & CONTINUE

What is saved?

The index, source locations and analysis are saved and can be refreshed. LogicLens reuses this project information where applicable.

GOOD TO KNOW

What you need to know

The index supports JavaScript, TypeScript, JSX, TSX, HTML and CSS. Potential dependencies do not guarantee complete runtime coverage; dynamic links may be missing.