Skip to content

refactor!: rename credential field apikey to api_key - #4

Merged
michielgerritsen merged 1 commit into
mainfrom
feat/field-naming
Jul 30, 2026
Merged

refactor!: rename credential field apikey to api_key#4
michielgerritsen merged 1 commit into
mainfrom
feat/field-naming

Conversation

@rhoerr

@rhoerr rhoerr commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

Summary

Canonicalizes credential field naming on snake_case: apikeyapi_key (in FieldFactoryTrait, ClientFactory config reads including the Azure arm, README examples, and tests). base_url/endpoint/model/deployment/api_version were already snake_case.

Breaking for any stored config created before this lands — acceptable pre-1.0.0, no migration shipped. SensitiveDataProcessor::SENSITIVE_KEYS intentionally keeps both spellings as a defensive measure for third-party providers.

PR chain (stacked on #2; each retargets as its base merges): Grok/xAI dedupe → api_key rename → masked credentials → CSP. All are pre-1.0.0, so the breaking changes need no migration.

Test plan

  • Unit tests updated to api_key; one legacy-spelling test retained for the defensive path.
  • vendor/bin/phpcs exits 0.

🤖 Generated with Claude Code

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.

2 participants