You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
thanks a lot for all the recent refactoring to support functions! I just updated my code base and found the following inconsistency:
While most Role properties changed from string to RoleType, the Role properties in the MessageResponse and StreamMessage classes are still of type string.
As I suppose the values can also just be "user" or "assistant", the RoleType enum could be used there as well, couldn't it?
As a workaround, I now have my own comparison utility.
The text was updated successfully, but these errors were encountered:
Hi,
thanks a lot for all the recent refactoring to support functions! I just updated my code base and found the following inconsistency:
While most
Role
properties changed fromstring
toRoleType
, theRole
properties in theMessageResponse
andStreamMessage
classes are still of typestring
.As I suppose the values can also just be "user" or "assistant", the
RoleType
enum could be used there as well, couldn't it?As a workaround, I now have my own comparison utility.
The text was updated successfully, but these errors were encountered: