NAME
Developer::Dashboard::Runtime::Result - helper accessors for dashboard hook RESULT JSON
SYNOPSIS
use Developer::Dashboard::Runtime::Result;
my $all = Developer::Dashboard::Runtime::Result::current();
my $mode = Developer::Dashboard::Runtime::Result::set_current($all);
my $stdout = Developer::Dashboard::Runtime::Result::stdout('00-first.pl');
my $last = Developer::Dashboard::Runtime::Result::last_entry();
Developer::Dashboard::Runtime::Result::clear_current();
DESCRIPTION
This module decodes the hook-result payload populated by dashboard command hook execution. Small payloads stay inline in RESULT. Oversized payloads spill into RESULT_FILE before later exec() calls would hit the kernel arg/env limit. The helper accessors hide that transport detail and provide one consistent way to read per-hook stdout, stderr, and exit codes from Perl hook scripts.
FUNCTIONS
current, set_current, clear_current, names, has, entry, stdout, stderr, exit_code, last_name, last_entry, report
Decode, write, clear, and report the current hook-result payload, whether it is stored inline in RESULT or spilled into RESULT_FILE.
PURPOSE
Perl module in the Developer Dashboard codebase. This file reads and writes the RESULT payload shared between layered command hooks. Open this file when you need the implementation, regression coverage, or runtime entrypoint for that responsibility rather than guessing which part of the tree owns it.
WHY IT EXISTS
It exists to keep this responsibility in reusable Perl code instead of hiding it in the thin dashboard switchboard, bookmark text, or duplicated helper scripts. That separation makes the runtime easier to test, safer to change, and easier for contributors to navigate.
WHEN TO USE
Use this file when you are changing the underlying runtime behaviour it owns, when you need to call its routines from another part of the project, or when a failing test points at this module as the real owner of the bug.
HOW TO USE
Load Developer::Dashboard::Runtime::Result from Perl code under lib/ or from a focused test, then use the public routines documented in the inline function comments and existing SYNOPSIS/METHODS sections. This file is not a standalone executable.
WHAT USES IT
This file is used by whichever runtime path owns this responsibility: the public dashboard entrypoint, staged private helper scripts under share/private-cli/, the web runtime, update flows, and the focused regression tests under t/.
EXAMPLES
perl -Ilib -MDeveloper::Dashboard::Runtime::Result -e 'print qq{loaded\n}'
That example is only a quick load check. For real usage, follow the public routines already described in the inline code comments and any existing SYNOPSIS section.