feat: add drive files patch metaapi#444
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 (2)
✅ Files skipped from review due to trivial changes (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughAdded documentation and skill metadata to document that file titles can be modified via the Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Suggested labels
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Nitpick comments (1)
skill-template/domains/drive.md (1)
12-12: Polish parameter formatting for consistency.Line 12 is clear functionally, but
new_titleis easier to scan if formatted as code and spaced consistently with the rest of this doc style.Suggested doc tweak
-- 使用 `drive files patch` 命令,通过new_title字段可以修改标题,支持 docx、sheet、bitable、file、wiki、folder 类型 +- 使用 `drive files patch` 命令,通过 `new_title` 字段修改标题,支持 `docx`、`sheet`、`bitable`、`file`、`wiki`、`folder` 类型。🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@skill-template/domains/drive.md` at line 12, Update the sentence that documents the drive files patch usage to format the parameter name `new_title` as inline code and ensure spacing matches the doc's style (e.g., backticks around `new_title` and consistent spaces after commas); locate the line referencing the `drive files patch` command and the list of supported types (docx, sheet, bitable, file, wiki, folder) and change `new_title` to be presented as `new_title` so it visually matches other parameters in the document.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@skills/lark-drive/SKILL.md`:
- Line 223: Update the `files.patch` capability description to match the
multi-type support used elsewhere: replace the current single-type text
("支持docx") with the full list used on Lines 4 and 25 (e.g.,
"支持docx/sheet/bitable/file/wiki/folder") so the `files.patch` entry is
consistent with the rest of the document.
- Line 274: The permission mapping for files.patch → base:app:update is
semantically inconsistent: locate the mapping in SKILL.md and the authoritative
registry entry in internal/registry/scope_priorities.json (search for
"files.patch" and "base:app:update") and either (A) justify and document why a
Drive file modification requires the Base-specific scope by adding an explicit
rationale in SKILL.md, or (B) change the mapping to a more appropriate Drive
scope (e.g., a drive-specific update scope used elsewhere like
"drive:files:update" or the existing Drive-related scopes in the registry) and
update both SKILL.md and the registry entry to match; ensure all other Drive
methods in the same table use domain-consistent scopes (e.g., docs:*, space:*)
and run registry validation to confirm no conflicts.
---
Nitpick comments:
In `@skill-template/domains/drive.md`:
- Line 12: Update the sentence that documents the drive files patch usage to
format the parameter name `new_title` as inline code and ensure spacing matches
the doc's style (e.g., backticks around `new_title` and consistent spaces after
commas); locate the line referencing the `drive files patch` command and the
list of supported types (docx, sheet, bitable, file, wiki, folder) and change
`new_title` to be presented as `new_title` so it visually matches other
parameters in the document.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 8c1bf2a3-11dd-4701-92cd-1165234d53a4
📒 Files selected for processing (2)
skill-template/domains/drive.mdskills/lark-drive/SKILL.md
Greptile SummaryThis PR is a documentation-only change: it adds a Confidence Score: 5/5Documentation-only PR; no code changes. Safe to merge once prior reviewer concerns about wiki token guidance are addressed. All remaining findings are P2 style suggestions. The two previously flagged P1-level concerns (scope inconsistency and wiki token guidance) were raised in prior review threads and partially addressed by the author; no new blocking issues were found. skills/lark-drive/SKILL.md line 274 (permission scope) and line 25 (wiki token guidance) warrant a final author check before merge. Important Files Changed
Reviews (2): Last reviewed commit: "feat: add drive files patch metaapi" | Re-trigger Greptile |
🚀 PR Preview Install Guide🧰 CLI updatenpm i -g https://pkg.pr.new/larksuite/cli/@larksuite/cli@dd155e2c5f0939d43192f0a3537aae0ef7c4109b🧩 Skill updatenpx skills add larksuite/cli#feat/drive-metaapi -y -g |
Change-Id: Ieb5b11f004c6007813f48d4312a7d6e476bd6d79
42b9477 to
dd155e2
Compare
Change-Id: Ieb5b11f004c6007813f48d4312a7d6e476bd6d79
Change-Id: Ieb5b11f004c6007813f48d4312a7d6e476bd6d79
Summary
Add the Drive
files.patchmeta API solark-cli drive files patchcan update Drive resource titles through the auto-generated service command layer. Update the Drive skill docs and template so agentsknow to use this command for file renaming flows.
Changes
drive.files.patchmetadata so the CLI exposeslark-cli drive files patchwithfile_token,type, andnew_titleskills/lark-drive/SKILL.mdandskill-template/domains/drive.md, including supported resource types such asdocx,sheet,bitable,file,wiki, andfolderTest Plan
lark xxxcommand works as expected./lark-cli drive files patchagainstdocx,folder, andwikiresources, and confirmed the updated titles via follow-up metadata/node queriesRelated Issues
Summary by CodeRabbit