Up to date Narrative last written —; no source changes since. Method signatures below are reflected live.

Debugger — Debug Mode Manager

File: src/Debugger.php Namespace: Magrathea2 Extends: Singleton

Central debug management for the framework. Controls verbosity of error output, query logging, and stack trace display. Integrates with MagratheaPHP's mode system.

Debug Levels

Constant	Value	Description
`Debugger::NONE`	0	No debug output
`Debugger::LOG`	2	Log to file only (default)
`Debugger::DEBUG`	3	Verbose debug with stack traces
`Debugger::DEV`	4	Full development mode

Properties

Property	Type	Default	Description
`$logFile`	`?string`	`null`	Path to the debug log file
`$debugItems`	`array`	`[]`	Collected debug entries
`$debugType`	`int`	`LOG`	Current debug level
`$queries`	`bool`	`false`	Whether query logging is enabled

Setting the Debug Level

`SetType(int $type): Debugger`

Set the debug level manually.

use Magrathea2\Debugger;
Debugger::Instance()->SetType(Debugger::DEV);

`SetDev(): Debugger`

Enable development mode (level DEV).

Debugger::Instance()->SetDev();

`SetDebug(): Debugger`

Enable debug mode (level DEBUG).

Debugger::Instance()->SetDebug();

`GetType(): int`

Returns the current debug level integer.

`GetTypeDesc(): string`

Returns the current level as a human-readable string.

Query Logging

`LogQueries(bool $q): Debugger`

Enable or disable SQL query logging.

Debugger::Instance()->LogQueries(true);

When enabled, every SQL query executed via Database is recorded and shown in the debug output.

Adding Debug Items

`Add(mixed $debug): void`

Add any value to the debug collection (string, array, object).

Debugger::Instance()->Add("Processing user #42");
Debugger::Instance()->Add(["step" => "validation", "passed" => true]);

`Info(string $debug): void`

Add an info-level string to the debug collection.

Debugger::Instance()->Info("Cache miss for: products_list");

`AddError(\Exception $err): void` / `Error(\Exception $err): void`

Record an exception.

try {
    // something risky
} catch (\Exception $e) {
    Debugger::Instance()->AddError($e);
}

`AddQuery(string $sql, ?string $values): void`

Manually add a query to the debug log.

Debugger::Instance()->AddQuery($sql, json_encode($values));

Displaying Debug Info

`Show(): void`

Output all collected debug items.

Debugger::Instance()->Show();

`Trace(): void`

Print the current stack trace.

Debugger::Instance()->Trace();

Log File

`SetLogFile(string $file): Debugger`

Set a file path for writing debug output.

Debugger::Instance()->SetLogFile("/var/log/myapp/debug.log");

Temporary Level Switching

Useful when you need to temporarily increase verbosity for a specific operation:

`SetTemp(string $dType): Debugger`

Temporarily switch to a different debug type.

`BackTemp(): Debugger`

Restore the previous debug type.

$debugger = Debugger::Instance();
$debugger->SetTemp("debug");
// ... do something with more logging ...
$debugger->BackTemp();

Integration with MagratheaPHP Modes

MagratheaPHP methods configure Debugger automatically:

// Dev() → Debugger::DEV, query logging off
MagratheaPHP::Instance()->Dev();

// Debug() → Debugger::DEV, query logging ON
MagratheaPHP::Instance()->Debug();

// Prod() → Debugger::LOG, query logging off
MagratheaPHP::Instance()->Prod();

Example: Request Debug Dump

use Magrathea2\Debugger;

// At the end of a request (dev only)
if (Debugger::Instance()->GetType() >= Debugger::DEV) {
    Debugger::Instance()->Show();
}

Notes

Debugger collects items in memory during a request — Show() outputs them all at once.
In production, debug output should never be shown to end users; use the Logger instead.
Query logging (LogQueries) can significantly impact performance — use only in dev/debug modes.

Class Reference — Debugger

Magrathea2\Debugger extends Singleton /home/platypusweb/platypusweb.com.br/site/magratheaphp2/src/Debugger.php

Magrathea Debugger can manage anything for debugging and error-searching through Magrathea Codes. It can trace errors, save log files, print queries and do a bunch of functions that would help the developer on error searching

Add($debug)

Add an item to the debug array object @param string $debug debug item

Param	Type	Default
`$debug`	mixed	required

AddError($err)

Adds an error to the debugger

Param	Type	Default
`$err`	mixed	required

AddQuery($sql, $values)

Adds a query to the debug

Param	Type	Default
`$sql`	mixed	required
`$values`	mixed	required

BackTemp()

After temporarily setting a debugging type, gets it back to what it was

Error($err)

Adds an error to the debugger

Param	Type	Default
`$err`	mixed	required

GetType()

Returns the debug type

GetTypeDesc(): string

Returns the debug type in a descritive format

Info($debug)

Add an info item to the debug array object @param string $debug info item

Param	Type	Default
`$debug`	mixed	required

LogQueries($q)

Should debugger log queries?

Param	Type	Default
`$q`	mixed	required

SetDebug()

Sets debug mode as debug

SetDev()

Sets debug mode as dev

SetLogFile($file)

Set the name of log file that will be used (it will be created inside "*logs*" folder)

Param	Type	Default
`$file`	mixed	required

SetTemp($dType)

Sets a debugger type temporarily (usefull when need to check a specific operation, for example)

Param	Type	Default
`$dType`	mixed	required

SetType($type)

Sets the debugger method It can be: *DEV*, *DEBUG*, *LOG*, *NONE* => **Debugger::DEV** = Will print the debugs as it appears in the code **Debugger::DEBUG** = Will store all the debugs and print it later **Debugger::LOG** = Will log queries and other debugs in the code **Debugger::ANALYSIS** = Will return the error with the API **Debugger::NONE** = Well... nothing to do, heh? Default: **LOG**

Param	Type	Default
`$type`	mixed	required

Show()

Prints the debug

Trace()

Trace error location

Examples

Logging & Debugging

From skills.MD

Debugger — Debug Mode Manager

Debug Levels

Properties

Setting the Debug Level

SetType(int $type): Debugger

SetDev(): Debugger

SetDebug(): Debugger

GetType(): int