/ 
Developer-Dashboard-2.17
/ Developer::Dashboard::Zipper

NAME

Developer::Dashboard::Zipper - older token encoding and ajax URL compatibility helpers

SYNOPSIS

use Developer::Dashboard::Zipper qw(zip unzip Ajax);
my $token = zip("print qq{ok\\n};");

DESCRIPTION

This module recreates the small token and ajax helper surface expected by older bookmark code without carrying forward any project-specific logic.

FUNCTIONS

zip, unzip, acmdx, Ajax, __cmdx, _cmdx, _cmdp

Encode and decode token payloads and generate older-style ajax links. Saved bookmark Ajax file handlers are stored under the dashboards ajax tree as executable files so the web runtime can run them as real processes.

PURPOSE

This module keeps the older bookmark and Ajax helper compatibility surface alive. It builds tokenised URLs, saved Ajax endpoints, and helper snippets such as Ajax() while routing the actual encoding work through the modern codec module.

WHY IT EXISTS

It exists because older bookmarks still expect the historical helper names and URL-building patterns. Keeping those wrappers in one module preserves compatibility without forcing newer runtime code to keep re-implementing the old API directly.

WHEN TO USE

Use this file when changing older Ajax helper behavior, saved Ajax file validation, token URL generation, or the compatibility wrappers that older bookmark instructions still reference.

HOW TO USE

Import the specific helper you need, such as zip, unzip, or Ajax, and let this module generate the compatibility structure or snippet. Newer code should prefer the lower-level runtime and codec modules where possible.

WHAT USES IT

It is used by older bookmark pages, by saved Ajax compatibility paths, by page-runtime helper injection, and by tests that guard the backward-compatible helper layer.

EXAMPLES

Example 1:

perl -Ilib -MDeveloper::Dashboard::Zipper -e 1

Do 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.t

Run the focused regression tests that most directly exercise this module's behavior.

Example 3:

HARNESS_PERL_SWITCHES=-MDevel::Cover prove -lr t

Recheck the module under the repository coverage gate rather than relying on a load-only probe.

Example 4:

prove -lr t

Put any module-level change back through the entire repository suite before release.