GitHub user Zhuoxi2000 added a comment to the discussion: [Discuss][API] Multimodal content parts in ChatMessage
The sequencing makes sense to me. Multimodal needs to land for 0.4 first, and that should leave #1056 with a cleaner surface to work from. A few boundaries I’d keep clear: 1. The block model lands once with multimodal. #1056 can then handle typed `tool_calls`, the `extra_args` → `metadata` rename, and moving response-level fields like usage/model/id without reshaping `blocks`. I’ll leave `tool_calls` and `extra_args` untouched in the multimodal change. 2. Blocks will use one serialization contract everywhere: Jackson/Pydantic, event attributes, and pemja, pinned by the cross-language snapshots. No new side path. 3. The existing Java/Python differences around `externalId` and `extra_args` stay in #1056. The multimodal converters won’t depend on those behaviors. Once multimodal lands, I’d also be happy to pick up part of #1056, especially typed `tool_calls` or the serialization cleanup. GitHub link: https://github.com/apache/flink-agents/discussions/1031#discussioncomment-18179011 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
