feat: 支持提交飞书原生「汇报」(report/record/entry) —— 当前 CLI 与 OpenAPI 均无写入接口
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 17.3k
- Forks
- 1.4k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 105
Description
需求
希望 lark-cli 支持填写 / 提交飞书原生「汇报」(即 oa.feishu.cn/report/record/entry 页面对应的写入动作,如日报 / 周报的提交)。
现状调研
查了飞书开放平台 report 模块,目前 OpenAPI 只开放了 3 个接口,全部为只读 / 管理类,没有任何提交汇报记录的写接口:
| 接口 | 方法 | 路径 |
|---|---|---|
| 查询规则 | GET | /open-apis/report/v1/rules/query |
| 查询任务 | GET | /open-apis/report/v1/tasks/query |
| 移除规则看板 | POST | /open-apis/report/v1/rule_views/remove |
lark-cli 也未封装 report 命令,且因为底层 OpenAPI 无写接口,用 lark-cli api 裸调同样无接口可用。
与 #74 的区别
#74 讨论的「日报」被作为群消息 / 云文档来读写处理。本 issue 特指飞书原生「汇报」模块(report/record/entry),即结构化的汇报规则 + 提交记录,二者不是一回事。
期望
- 如果 OpenAPI 后续开放了汇报提交接口,希望
lark-cli封装report写命令(提交 / 编辑汇报记录); - 如果短期内 OpenAPI 不会开放写能力,希望在文档 / skill 中明确说明「汇报内容无法通过 API 提交」,避免使用者反复踩坑。
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the report endpoints listed in the issue and the existing lark-cli api path first. Confirm whether a write endpoint exists; done means either a report submit/edit command once supported, or documentation or skill text clearly stating that report submission is unavailable through the API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, openapi
- Domain
- api, cli, documentation
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100