Skip to content

feat: change vendor Options extra='forbid' to extra='allow' and forwa…#1

Merged
HugoChaan merged 2 commits intomainfrom
feat/extra-allow-forward-extra-fields
Mar 18, 2026
Merged

feat: change vendor Options extra='forbid' to extra='allow' and forwa…#1
HugoChaan merged 2 commits intomainfrom
feat/extra-allow-forward-extra-fields

Conversation

@qinhui-agora
Copy link
Copy Markdown
Collaborator

…rd extra fields in to_config()

  • Change all Pydantic Config extra='forbid' to extra='allow' across all vendor Options classes (llm, tts, stt, avatar)
  • Update all to_config() methods to forward model_extra into output config/params dict
  • Rename Python module from 'agent' to 'shengwang_agent' to avoid naming conflicts
  • Update pyproject.toml packages entry accordingly

This allows users to pass additional vendor-specific fields that are not explicitly defined in the Options classes, and have them forwarded to the API request payload.

qinhui and others added 2 commits March 18, 2026 19:17
…rd extra fields in to_config()

- Change all Pydantic Config extra='forbid' to extra='allow' across all vendor Options classes (llm, tts, stt, avatar)
- Update all to_config() methods to forward model_extra into output config/params dict
- Rename Python module from 'agent' to 'shengwang_agent' to avoid naming conflicts
- Update pyproject.toml packages entry accordingly

This allows users to pass additional vendor-specific fields that are not explicitly
defined in the Options classes, and have them forwarded to the API request payload.
@HugoChaan HugoChaan merged commit 7f56ba6 into main Mar 18, 2026
3 checks passed
@HugoChaan HugoChaan deleted the feat/extra-allow-forward-extra-fields branch March 18, 2026 11:44
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.

3 participants