Agent-First Data v0.38.0: Linting Suffixes in Collections and Config Text
afdata lint now checks suffixed arrays element by element, parses dotenv and INI suffix values as numeric text, and flags plural or array-valued names that lack a suffix. The CLI spec builder also allows shorter option names for sensitive arguments.
Unit and type suffixes only earn their keep when the linter enforces them everywhere they appear—inside arrays, inside flat config formats where every value is text, and on collection names that forgot to carry one.
Linting suffixed arrays and flat config formats
afdata lint previously checked suffixed scalar fields directly, which left
two blind spots:
- Element-by-element array linting. When an array field carries a suffix, each element is now validated against that suffix rather than stopping at the container.
- Dotenv and INI numeric text. In formats where every value is parsed as a
string, suffixed fields are now read as numeric text before suffix validation
runs, so valid numbers in
.envand.inifiles pass without false positives. - Plural and array-valued stem names without a suffix. Fields whose names
are plural forms of suffix-requiring stems (such as
timeoutsorsecrets) or whose values are arrays of those stems are now flagged when they omit a suffix.
Shorter option names for sensitive arguments
In the Rust cli_spec builder, sensitive arguments no longer require long
option names—shorter option names are now accepted when declaring sensitive
flags.