fix(feishu): nest card elements under body — schema 2.0 rejects top-level elements - #3
Merged
Merged
Conversation
…evel elements Caught in the first real-device e2e (2026-07-15): the real API refuses build_card()'s output with 200621 'parse card json err: unknown property elements at path []' — schema-2.0 cards put elements under body; top-level elements is the v1 location. Verified live after the fix: inbound feishu message → agent run → interactive card reply renders in the chat. Claude-Session: https://claude.ai/code/session_014iw5PBsSzDFHus1GfkAK4y
bigduu
added a commit
to bigduu/Bamboo-agent
that referenced
this pull request
Jul 15, 2026
…ts top-level elements (#484) Same defect Magpie's first real-device e2e caught in its ported copy (bigduu/Magpie#3): the real im/v1/messages API refuses the card with 200621 'parse card json err: unknown property elements at path []' — schema-2.0 cards put elements under body; top-level is the v1 location. Every in-proc feishu card send/edit fails until this lands. Fix verified live against real Feishu via the identical magpie builder. Claude-Session: https://claude.ai/code/session_014iw5PBsSzDFHus1GfkAK4y Co-authored-by: bigduu <mugeng.du@gmail.com>
bigduu
added a commit
that referenced
this pull request
Jul 15, 2026
…rows out with column_set (#7) Second real-API rejection the 2026-07-15 e2e caught (right after #3's body-nesting fix): sending a card with a tag:"action" row fails with 200861 'cards of schema V2 no longer support this capability: unsupported tag action'. Button rows are now a column_set with one weighted column per button (buttons keep the pinned behaviors/value.cb shape). Live-verified: the options-question card renders with working [OASIS]/[LAGOON] buttons. Claude-Session: https://claude.ai/code/session_014iw5PBsSzDFHus1GfkAK4y Co-authored-by: bigduu <mugeng.du@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
First real-device Feishu e2e (epic bamboo#477 tail) caught this immediately:
im/v1/messagesrefuses every card magpie sends withbuild_card()emitted{"schema":"2.0", "config":…, "elements":[…]}— but schema 2.0 nestselementsunderbody; a top-levelelementsis the v1 location. The code comment even flagged this exact spot as "protocol shape inferred rather than verified".Fix:
"body": {"elements": […]}. Same card JSON feeds both send and the PATCH edit path, so one change covers both.Live-verified end-to-end after the fix: Feishu web → WS long-connection → allow_from → bridge → bamboo /v2 (device token) → agent run → streaming card reply
✅ MAGPIE-E2E-OKrendered in the chat. wiremock tests updated (content["body"]["elements"]); 45 feishu tests green.https://claude.ai/code/session_014iw5PBsSzDFHus1GfkAK4y