Documentation

Graphtia documentation · concept

Neighborhoods

Explore a bounded area around a selected file or symbol.

A useful amount of nearby context

A neighborhood is a bounded view around a selected entity. It is useful when you need to orient yourself before asking a more specific dependency, call or impact question. Its center gives the investigation a stable reference point.

From entry point to supporting code

The checkout entry point reaches a service, its payment and order dependencies, a validation contract and a test. Lines illustrate static relationships, not runtime execution.

Entry pointcheckout.test.ts
01
Checkout servicecheckout-service.ts
02
Payment gatewaypayment-gateway.ts
03
Order moduleorder-service.ts
04
Validation contractvalidation.ts
05
Related checkscheckout.test.ts
06
Selected module · Static relationships · Supporting checks

Start small, then follow the question

A neighborhood around checkout-service.ts can include its module dependencies, contained symbols and nearby consumers. These are different relationships. Read their kinds instead of treating proximity on the screen as a measure of business importance.

  • Keep the selected entity identifiable as you inspect nearby code.

  • Use a relationship-specific view when a general neighborhood becomes noisy.

  • Expand only when an unanswered question requires another step.

  • Check the result envelope and current revision before recording an observation.

Depth and visual layout are different

Query depth limits how far the traversal may move through relationships. Screen distance reflects the layout of the current view. A node drawn close to the center is not necessarily a direct caller, and a visually separate cluster may still share a boundary.

Graphtia

This page is on its way. Join the waitlist to hear what’s next for Graphtia.

Join waitlist