Today, the 'Content' property of the 'ChatMessageContent' class serves as a shortcut for the first item of the TextContent type. This can be confusing for consumer code, in cases where a message contains multiple items of the TextContent type.
The proposal here is to mark the 'Content' property as obsolete and eventually removing it after providing consumers with sufficient time to migrate to using the Items collection.
Today, the 'Content' property of the 'ChatMessageContent' class serves as a shortcut for the first item of the TextContent type. This can be confusing for consumer code, in cases where a message contains multiple items of the TextContent type.
The proposal here is to mark the 'Content' property as obsolete and eventually removing it after providing consumers with sufficient time to migrate to using the Items collection.
More details - https://github.com/microsoft/semantic-kernel/pull/5088#discussion_r1498844180