Struct DocumentDiscoveryPlugin 

pub struct DocumentDiscoveryPlugin;

Plugin that auto-discovers document files from configured directories.

Scans directories specified in option "documents" for files matching the pattern: {Account}/YYYY-MM-DD.description.*

For example: documents/Assets/Bank/Checking/2024-01-15.statement.pdf generates: 2024-01-15 document Assets:Bank:Checking "documents/Assets/Bank/Checking/2024-01-15.statement.pdf"

Configuration

The plugin reads its per-load context (resolved document directories and the ledger’s base directory for relative-path normalization) from PluginInput::config as a JSON object:

{"base_dir": "/path/to/ledger", "directories": ["/abs/path/docs"]}

The loader constructs this config when populating the synth pass; if config is None or directories is empty, the plugin returns a no-op (every input directive is kept, nothing synthesized). If config is present but malformed JSON, every input directive is still kept and a PluginError::error is added to the output errors — the plugin never silently drops directives on bad config. This lets the plugin sit in the registry as a static instance and be dispatched through the normal synth-pass machinery.

Security

• Symlinks are skipped to prevent infinite recursion from symlink cycles
• Maximum recursion depth is enforced to prevent denial-of-service from deeply nested directories

Trait Implementations

impl NativePlugin for DocumentDiscoveryPlugin

fn name(&self) -> &'static str

Plugin name (short form — "implicit_prices", not the fully-qualified module path).

fn description(&self) -> &'static str

Plugin description for --help and similar UI surfaces.

fn process(&self, input: PluginInput) -> PluginOutput

Process directives and return modified directives + errors.

impl SynthPlugin for DocumentDiscoveryPlugin

Synthesizes Document directives that downstream consumers expect alongside user-written ones — runs in the synth pass so the early validator sees them.