docs(calendar): document setting meeting owner via full API#1903
Merged
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthrough更新会议室创建 API 差异说明,补充会议 owner 的配置字段、调用身份、日历类型及 owner 标识限制。 Changes日历 API 文档
Estimated code review effort: 1 (Trivial) | ~2 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1903 +/- ##
=======================================
Coverage 74.72% 74.72%
=======================================
Files 886 886
Lines 92621 92621
=======================================
Hits 69208 69208
Misses 18052 18052
Partials 5361 5361 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
🚀 PR Preview Install Guide🧰 CLI updatenpm i -g https://pkg.pr.new/larksuite/cli/@larksuite/cli@2ed99c5ebc72e11d5db5c7df3ed351bd8542b7bc🧩 Skill updatenpx skills add larksuite/cli#docs/calendar-meeting-owner -y -g |
Note that meeting owner must be set via vchat.meeting_settings.owner_id with vchat.vc_type=vc, effective only for app (bot) identity on app calendars, since +create does not expose this field.
calendar-assistant
force-pushed
the
docs/calendar-meeting-owner
branch
from
July 15, 2026 11:20
5f0f7a1 to
2ed99c5
Compare
zhangjun-bytedance
approved these changes
Jul 15, 2026
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
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.
Summary
When creating a calendar event, if the caller wants to set the meeting owner, the
+createshortcut does not expose this field. This documents how to set it via the full API command so AI agents route to the correct path.Changes
lark-calendar-create.md: set the meeting owner viavchat.meeting_settings.owner_id, which requiresvchat.vc_type=vc, is effective only for app (bot) identity operating on an app calendar, and the owner must be a user (ou_open_id), not a non-user or external-tenant user.Test Plan
Related Issues
Summary by CodeRabbit
+createAPI.