Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions fern/definition/messages.yml
Original file line number Diff line number Diff line change
Expand Up @@ -90,7 +90,9 @@ types:
message_id: MessageId
labels: MessageLabels
timestamp: MessageTimestamp
from: MessageFrom
from:
type: MessageFrom
docs: Address of sender. Note - since `from` is a reserved keyword in Python, access this field as `from_` when using the Python SDK (e.g. `message.from_`).
to: MessageTo
cc: optional<MessageCc>
bcc: optional<MessageBcc>
Expand All @@ -111,8 +113,10 @@ types:
message_id: MessageId
labels: MessageLabels
timestamp: MessageTimestamp
from: MessageFrom
reply_to:
from:
type: MessageFrom
docs: Address of sender. Note - since `from` is a reserved keyword in Python, access this field as `from_` when using the Python SDK (e.g. `message.from_`).
reply_to:
Copy link
Copy Markdown
Contributor

@cubic-dev-ai cubic-dev-ai Bot Mar 17, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1: Malformed indentation in Message.properties breaks YAML/Fern structure and moves reply_to out of the Message schema.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At fern/definition/messages.yml, line 119:

<comment>Malformed indentation in `Message.properties` breaks YAML/Fern structure and moves `reply_to` out of the `Message` schema.</comment>

<file context>
@@ -111,8 +113,10 @@ types:
+      from:
+              type: MessageFrom
+        docs: Address of sender. Note - since `from` is a reserved keyword in Python, access this field as `from_` when using the Python SDK (e.g. `message.from_`).
+reply_to:
         type: optional<list<string>>
         docs: Reply-to addresses. In format `username@domain.com` or `Display Name <username@domain.com>`.
</file context>
Fix with Cubic

type: optional<list<string>>
docs: Reply-to addresses. In format `username@domain.com` or `Display Name <username@domain.com>`.
to: MessageTo
Expand Down