The graph is a map of your code made of things and links. The things are parts of your code, such as methods, classes, files, routes, tables and events. The links say how they relate: this method calls that one, this class extends that one, this method writes to that table.

An everyday comparison: a family tree, but for code. You can start from any person and walk to their parents, their children, or their cousins.

What is in it

Things (nodes) Links (edges)
Methods and constructors, classes, interfaces, enums, files (modules), outside libraries, outbound HTTP calls, data stores (tables, collections, queues), events Calls; has-method; imports; uses-type; returns; extends; implements; overrides; reads-from, writes-to, deletes-from (data); calls-HTTP; handled-by (a route to the method that serves it); triggers-event and event-handled-by

What is not in it: your source code. The graph keeps names, places (file and line) and links. When a tool shows you code, it reads the file from disk at that moment.

How it is built

  1. Niro reads each source file and works out its structure. This step is called parsing.
  2. It then matches every name used to the thing it names, across the whole project. This step is called resolving. For example, it finds which send method a call to send() reaches.
  3. It recognises routes, outbound calls, data access and events from tables of known libraries and frameworks.

Building and keeping it current: Builds and updates.

How to read an answer

What it cannot see

The known gaps, by kind, are in FAQ: wrong or missing answers.