Skip to content

fix: support file input for IM message content#8

Open
hehanlin1996 wants to merge 1 commit into
mainfrom
ai-fix-20260517-im-content-input
Open

fix: support file input for IM message content#8
hehanlin1996 wants to merge 1 commit into
mainfrom
ai-fix-20260517-im-content-input

Conversation

@hehanlin1996
Copy link
Copy Markdown
Owner

Summary

Fix feedback C5/larksuiteGH-916 for im +messages-send so --content @card.json and --content - are resolved before JSON validation and dry-run/request construction.

Changes

  • Marked the content flag as accepting common file and stdin input sources.
  • Updated --content help text to document @file and stdin usage.
  • Added dry-run E2E coverage for interactive message content loaded from both a JSON file and stdin.

Test Plan

  • Unit tests pass: go test -buildvcs=false ./shortcuts/im -run 'TestShortcutValidateBranches|TestShortcutDryRunShapes' -count=1
  • Manual local verification confirms the lark xxx command works as expected: go test -buildvcs=false ./tests/cli_e2e/im -run 'TestMessagesSendDryRun_Content(File|Stdin)$' -count=1
  • Formatting checked: gofmt -l shortcuts/im/im_messages_send.go tests/cli_e2e/im/messages_send_dryrun_test.go

Related Issues

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant