Skip to content

fix: warn when unsupported parameters are silently ignored#212

Merged
Kamilbenkirane merged 2 commits intomainfrom
fix/unsupported-param-warning
Mar 19, 2026
Merged

fix: warn when unsupported parameters are silently ignored#212
Kamilbenkirane merged 2 commits intomainfrom
fix/unsupported-param-warning

Conversation

@Kamilbenkirane
Copy link
Member

Summary

Fixes #210

  • Adds UnsupportedParameterWarning(UserWarning) custom warning class
  • Emits warnings.warn() in _build_request() when a user passes a parameter that has no mapper for the current provider/model
  • Users can suppress with warnings.filterwarnings("ignore", category=UnsupportedParameterWarning) or promote to error with "error"

Test plan

  • Unit test: warning emitted for unsupported parameter
  • Unit test: no warning for supported parameters
  • Unit test: no warning when unsupported param value is None
  • All 505 existing tests pass

Fixes #210

Add UnsupportedParameterWarning emitted via warnings.warn() when a user
passes a parameter that has no mapper for the current provider/model.
@claude
Copy link

claude bot commented Mar 19, 2026

Code review

No issues found. Checked for bugs and CLAUDE.md compliance.

…aram detection

Each mapper claims its parameter via pop(). Unclaimed params are
naturally what remains, removing the need for a separate set + loop.
@Kamilbenkirane Kamilbenkirane merged commit 3246627 into main Mar 19, 2026
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

When a user passes a parameter that a provider doesn't support, Celeste silently ignores it. No error, no warning.

1 participant