chore: refactored state to pydantic #58#62
Conversation
navalnica
changed the title
|
/deploy-review
|
…e.init_from_response method
|
/deploy-review
|
navalnica
changed the title
navalnica
changed the title
navalnica
changed the title
|
/deploy-review
|
…o control whether to enable ev commands
|
/deploy-review
|
| direct_tool_calls: list[LangChainToolCall] = Field(default_factory=list) | ||
| tool_messages: list[StatGPTMessage] = Field(default_factory=list) | ||
|
|
||
| model_config = ConfigDict(validate_assignment=True, extra="forbid") |
There was a problem hiding this comment.
using extra='forbid' could be a breaking change triggered on older existing conversations (they might have additional fields specified in the state). though I think this might be ok - we can add this to the "breaking changes" list on our next release.
however, it's a safer option for the future development
alternatively, we can set extra='ignore'. this is safer to existing conversations. but this might introduce bugs during future development
@Fedir-Yatsenko , what do you think?
atomao
changed the title
|
/deploy-review
|
|
/deploy-review
|
2 participants
Applicable issues
Description of changes
dicttopydanticschemaany_tool_response_failed- used by eval frameworkChecklist
By submitting this pull request, I confirm that my contribution is made under the terms of the MIT license.