docs +create: <ol seq="auto"> 返回 degrade_code=5002，但 skill 文档要求写该属性
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- go
- Domain
- documentation
Research direction
Read skills/lark-doc/references/lark-doc-xml.md around line 22 and compare its seq guidance with the warning reproduced by the docs +create command. Check the XML schema or validation path for ordered lists to determine whether col supports seq; done means either the behavior matches the documentation without a warning, or the documentation clearly explains that ordered lists do not support this attribute.
Written by the indexing model from the issue text.
Description
环境
- lark-cli 1.0.97（npm 全局安装），macOS，identity=user
- 命令：
lark-cli docs +create --doc-format xml --content @draft.xml --format json
复现
按 skill 文档写有序列表属性：
<ol seq="auto">
<li><p>第一项</p></li>
<li><p>第二项</p></li>
</ol>
实际
ok: true，但返回 warnings：
degrade_code=5002,msg=Unsupported attribute "seq" on <ol> is not in schema.
Check whether the generated attribute is expected by the target DocxXML tag
期望
要么无警告；要么 <ol> 确实不支持 seq 时，skill 文档不要要求作者写它。
冲突点
skills/lark-doc/references/lark-doc-xml.md 第 22 行写着：
有序列表：默认属性
seq="auto"，需从指定数字开始时设置对应值，如seq="3"。
同一份文档里 <h1 seq="auto"> 是有效的（创建后正确生成 seq-marker，无警告），所以作者会自然把同一写法用到 <ol> 上。
"从指定数字开始"（seq="3"）这个用法在文档里也没有别的入口说明。
影响
- 每次用有序列表创作都会带一条 warning。
- 把 warning 当可操作信号的 agent 会去找问题，但
<ol>在docs +fetch --detail with-ids里没有 block id（只有子级<li>有），无法用docs +update定位修复。 - 编号本身渲染正常（默认自增，
<li>上带seq-marker），所以这是一条无法消除、又无实际损坏的噪声警告。
建议
二选一：
- 服务端接受
<ol>的seq（含seq="3"起始编号），与文档对齐； - 或更新
lark-doc-xml.md，明确seq只适用于标题与列表项，有序列表无需也无法显式设置。
- Dominant language
- Go
- Stars
- 17.5k
- Forks
- 1.4k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 31
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
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.
More from larksuite/cli
-
domain/core domain/doc enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
domain/core domain/mail enhancement
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
docs: update README skill counts to the 28 shipped skillsPossibly taken @dajiaohuang claimed this 45 days ago. Opendomain/core
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
fix(slides): make IconPark JSON output safe on non-UTF-8 Windows consolesPossibly taken @dajiaohuang claimed this 45 days ago. Openbug domain/core
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
fix(binding): accept files nested under trusted directories on WindowsPossibly taken @dajiaohuang claimed this 45 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
Similar issues
-
agent-research agent-review-finding chore
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
jordansmall/spindrift#4922 ·
Maintainers usually reply within 1 day
-
gcsartifact: deleting a missing version returns an errorPossibly taken @ktsoator claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
govulncheck
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Change wording for init command success messagePossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
enhancement pkg:sdk
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
aws/aws-durable-execution-sdk-go#144 ·
Maintainers usually reply within 1 day