NAME

propq - Java properties query command for Developer Dashboard

SYNOPSIS

dashboard propq [path] [file]

DESCRIPTION

This command provides Java properties path extraction for Developer Dashboard.

PURPOSE

This staged helper owns the public dashboard propq command. It accepts an optional Java-properties key path plus an optional input file, then hands the request to the shared query runtime so parsing, file-vs-STDIN handling, and output formatting stay consistent with the rest of the dashboard toolchain.

WHY IT EXISTS

It exists because the dashboard ships a private, repo-local Java properties inspection tool instead of depending on a globally installed parser binary. Keeping propq as a staged helper also preserves the thin-switchboard contract in bin/dashboard.

WHEN TO USE

Use this file when you are changing how dashboard propq chooses between STDIN and files, how it reports parse errors, or how the staged helper is wired into the shared query implementation.

HOW TO USE

Users run dashboard propq [path] [file]. The staged helper selects the Java-properties backend in the shared query runtime, which accepts the file and path in either order, reads STDIN when no file is given, preserves dotted keys such as alpha.beta, and prints the whole parsed document when the path is $d or ..

WHAT USES IT

It is used by the public dashboard propq command, by shell snippets that want a runtime-local Java properties query tool, by integration smoke runs, and by the focused query-helper coverage under t/.

EXAMPLES

printf 'alpha.beta=5\nname=demo\n' | dashboard propq alpha.beta
dashboard propq app.properties '$d'
dashboard propq '$d' app.properties
printf 'name = demo\n' | dashboard propq name