Skip to content

logging data flow ​

A small tested application

Project overview

This view opens the logging folder one level deeper. Each arrow shows the called operation and the data it returns to its caller. Calls inside a file stay in that file’s sequence view.

100%
Mermaid source
flowchart TD
    n0["calculator"]
    n1["logger"]
    n0 -->|"Logger.log(message)"| n1

Package boundaries ​

console package calls
100%
Mermaid source
flowchart LR
    n0["august/io"]
    n1["console"]
    n1 -->|"Console.write(value)"| n0

Follow the data ​

Each row opens the complete operations and call sites behind one pair of logical units. A grouped arrow records calls between those units; connected arrows need not belong to the same execution path.

FromToOperationsRead
calculatorlogger1Inputs, results and call sites
consoleaugust/io1Inputs, results and call sites

Data crossing these boundaries (2 contracts) ​

calculator → logger ​

1 operation, 1 site

Logger.log · interface dispatch

Inputs: message: string. Result: void.

Caller or entryEvidence
Calculator.addCall site · Caller explanation

console → august/io ​

1 operation, 1 site

Console.write · interface dispatch

Inputs: value: string. Result: void.

Caller or entryEvidence
ConsoleLogger.logCall site · Caller explanation

What this folder exposes ​

Exports ​

Export the declaration Logger from logger.aug. Export the declaration ConsoleLogger from console.aug.

Files in this folder ​

ModuleRead
logging/console.augFlow and sequences · Explanation
logging/export.augFlow and sequences · Explanation
logging/logger.augFlow and sequences · Explanation

Last updated:

The world runs on language