GitHub user Zhuoxi2000 added a comment to the discussion: [Discuss][API] Multimodal content parts in ChatMessage
Agreed on all four. I’ve folded these into the proposal above. 1. Event Log: I’ll use the metadata only shape you suggested for every log level, including VERBOSE. Media payloads won’t be written to the Event Log. URL query strings will also be stripped so signed parameters don’t end up in logs. 2. URL vs managed references: for 0.4, I’ll keep this to inline base64 and externally managed URLs. No managed blob storage yet. The model will leave room for something like `blob_id` later without changing the overall design. The docs will also make it clear that URLs are external references, not durable storage. 3. `extra_args`: agreed that blocks should become the canonical representation of message content. `anthropic_content_blocks` can be deprecated once Anthropic moves to the new block model. I’ll leave `extra_args` itself unchanged here and keep the broader metadata cleanup in #1056. 4. Naming: agreed on `blocks: List<ContentBlock>` as the single source of truth, with no separate string content field. GitHub link: https://github.com/apache/flink-agents/discussions/1031#discussioncomment-18179004 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
