tamada / fauxrest

86%

main: 87%

LAST BUILD ON BRANCH fix/static-spec-error-messages

branch: fix/static-spec-error-messages

CHANGE BRANCH

x

Reset

Sync Branches

• fix/static-spec-error-messages
• ci/force_fmt_in_CI
• docs/changelog
• docs/function-comments
• docs/powered-by-badge
• feat/derive-from-filtered-data
• feature/overwrite-option
• feature/static-file-copy
• feature/trim-derive-type
• fix/cli-options-override
• fix/config-error-messages
• fix/docs-deploy-workflow
• fix/no-partial-output-on-failure
• fix/publish-cargo-lock-sync
• fix/reject-mixed-field-types
• fix/string-ordering-comparison
• fix/validate-filter-regex
• main
• releases/v0.0.1
• releases/v0.0.2
• releases/v0.0.3
• releases/v0.0.4

Build # 30678787283

Build Type

Pull #20

github

Committed by tamada

Commit Message

fix: report the actual cause of $static config errors too

#17 gave `DeriveSource`, `AggregateSpec` and `AggregateSource` hand-written
`Deserialize` impls so their failures name a cause. `StaticSpec` has the same
`#[serde(untagged)]` shape and was missed — issue #16 listed only the first
three, and so did I.

    $static: 42          →  data did not match any variant of untagged enum StaticSpec
    {"include": [42]}    →  same

Now:

    $static: 42          →  $static must be a list of globs or an object, got number
    {"include": [42]}    →  invalid type: integer `42`, expected a string

Shipping a release that advertises "config errors name what is wrong" while one
of four directives still did not would have been a poor look, so this goes in
0.0.4 alongside the rest.

Parsing behaviour is unchanged: the shorthand `["*.png"]` and the full form with
`exclude` both still resolve as before, verified by copying a data directory
through each and checking which files landed.

`$static` is now also covered by `test_config_errors_name_what_is_wrong`, which
grows from eight cases to ten.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Pull Request Pull Request #20: fix: report the actual cause of $static config errors too

Coverage Stats

12 of 0 new or added lines in 0 files covered. (NaN%)

44 existing lines in 1 file now uncovered.

1370 of 1588 relevant lines covered (86.27%)

15.13 hits per line