Graphtia documentation · workflow
Projects
Use a project as the boundary for a code-understanding investigation.
Choose a meaningful repository root
A project provides the source boundary for indexing. Start at the repository or workspace root so the analyzer can see relevant package metadata and local modules together. Selecting a single nested folder may hide relationships that cross the selected boundary.
Open, inspect, then scan
Add a project and select its source folder. Review the detected path and project information.
Start the initial scan. Wait for its reported result rather than treating a queued or scanning state as complete.
Open the project, check its currentness state and use the file tree or symbol search to find a known source location.
When a file is missing
Check the selected root, language support and excluded or generated paths. Also distinguish a file that is not indexed from a symbol that is indexed but not present in the current bounded view. Search and the tree can help narrow that distinction.
After source changes
Read the project state and source notices again. A scan can be needed after changes or when the persisted index no longer matches the current source. Incremental behavior is still being validated across larger workspaces.