/ 
Developer-Dashboard-2.17
/ Developer::Dashboard::File

NAME

Developer::Dashboard::File - older file compatibility wrapper

SYNOPSIS

File->configure(aliases => { output => '/tmp/output.txt' });
File->write(output => "ok\n");

DESCRIPTION

This module provides a minimal compatibility wrapper for older bookmark code that references a File package directly.

METHODS

configure, read, write

Configure and read or write compatibility files.

PURPOSE

This module is the narrow compatibility wrapper for older bookmark code that still expects a top-level File package with alias-aware read and write methods. It maps friendly aliases to real paths and then performs the requested file operation.

WHY IT EXISTS

It exists to keep older bookmark snippets working while the rest of the runtime uses newer namespaced modules. The compatibility surface is intentionally tiny so the old API does not leak further into new code.

WHEN TO USE

Use this file when a compatibility bookmark or test still relies on File->read, File->write, or File->configure, or when you need to tighten the behavior of that old alias mechanism without breaking the compatibility contract.

HOW TO USE

Call configure once with any alias map you need, then use read or write with either the alias or the concrete path. Treat it as a compatibility shim, not as the main runtime file abstraction.

WHAT USES IT

It is used by older bookmark code paths, by compatibility tests, and by release documentation that keeps the backward-compatible helper layer visible to maintainers.

EXAMPLES

Example 1:

perl -Ilib -MDeveloper::Dashboard::File -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.