NAME
Developer::Dashboard::DataHelper - older JSON helper compatibility functions
SYNOPSIS
use Developer::Dashboard::DataHelper qw(j je);
my $json = j({ ok => 1 });DESCRIPTION
This module provides the small older JSON helper functions used by older bookmark code blocks.
FUNCTIONS
j, je
Encode and decode JSON values.
PURPOSE
This module keeps the tiny j() and je() compatibility helpers used by older bookmark code blocks. It maps those short names onto the project-standard JSON::XS encoder and decoder so older bookmark snippets can keep working without dragging a larger helper layer into the page runtime.
WHY IT EXISTS
It exists because some bookmark code still expects the older helper names. Preserving them in one compatibility module lets the runtime stay backward-compatible without letting old helper naming spread through new code.
WHEN TO USE
Use this file when you are touching older bookmark snippets that call j() or je(), or when the project-wide JSON behavior changes and the compatibility layer has to stay in sync.
HOW TO USE
Import j and je in the bookmark or compatibility path that needs them. Newer runtime code should normally prefer Developer::Dashboard::JSON, but this module remains the right place for the short historical helper names that old bookmark snippets still call.
WHAT USES IT
It is used by older bookmark code, by compatibility-oriented tests, and by release metadata that keeps the shipped compatibility surface explicit.
EXAMPLES
Example 1:
perl -Ilib -MDeveloper::Dashboard::DataHelper -e 1Do a direct compile-and-load check against the module from a source checkout.
Example 2:
prove -lv t/21-refactor-coverage.t t/00-load.tRun the focused regression tests that most directly exercise this module's behavior.
Example 3:
HARNESS_PERL_SWITCHES=-MDevel::Cover prove -lr tRecheck the module under the repository coverage gate rather than relying on a load-only probe.
Example 4:
prove -lr tPut any module-level change back through the entire repository suite before release.