-
Notifications
You must be signed in to change notification settings - Fork 12
Open
Description
When messages are explicitly constructed, they should (and used to, prior to 0.7.11) come with their appropriate role.
For example, the following should be (and were) all valid instantiations where the role model would come with the message type, 'user' for UserMessage, 'system' for SystemMessage, 'assistant' for AssistantMessage:
UserMessage(content=msg.text)
AssistantMessage(content=msg.text)
SystemMessage(content=msg.text)
As of 0.7.11, this no longer works as expected, forcing the user to pass the role explicitly even to specific message types.
Not sure if something changed in the API definition that caused Speakeasy to cause this regression, but it is a regression, if minor.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels