Skip to content

Document generated SDK docs conventions in CLAUDE.md - #5259

Open
jeremyrose-viam wants to merge 2 commits into
viamrobotics:mainfrom
jeremyrose-viam:docs/claude-md-generated-sdk-docs
Open

Document generated SDK docs conventions in CLAUDE.md#5259
jeremyrose-viam wants to merge 2 commits into
viamrobotics:mainfrom
jeremyrose-viam:docs/claude-md-generated-sdk-docs

Conversation

@jeremyrose-viam

Copy link
Copy Markdown
Contributor

What this adds

A new "Generated SDK reference docs" section in CLAUDE.md, covering conventions that only live in code comments or CI config today and cost real time to rediscover:

  • static/include/**/apis/generated/*.md (and -table.md) are generated by update_sdk_methods.py from sdk_protos_map.csv — don't hand-edit them.
  • They're not covered by the pre-PR prettier/markdownlint checks documented earlier in this file (prettier-lint.yml only checks docs/**/*.md; markdown-lint.yml excludes static/ outright). Running prettier --write on them introduces unrelated reformatting noise. make build-prod still applies.
  • update_sdk_methods.py's actual Python dependencies (beautifulsoup4, markdownify) aren't in requirements.txt (that file is for the docs.yml index-sync jobs) — the authoritative list is the pip install line in check-methods.yml.
  • How the proto-override system works: one hand-written file per proto (static/include/<app|components|services|robot>/apis/overrides/protos/<resource>.<ProtoName>.md) supplies the plain-English description, since method signatures/params/examples are scraped live from each SDK's docs site but descriptions aren't. A missing override doesn't fail the build, just leaves a blank description with a coverage-job warning. No README covers this — only comments around update_sdk_methods.py's write_markdown().
  • A running list of resources deliberately excluded from sdk_protos_map.csv (currently just navigation, restored as a deprecated orphan page in Restore SLAM and navigation reference pages as deprecated orphan pages #5191) so a real coverage gap isn't mistaken for a bug, or vice versa.

Why

Came up repeatedly while resolving stale conflicts on #5186/#5187 (the SDK-method-coverage backlog series) — this is the same context, just made durable and shared instead of re-derived per PR.

Verification

Doc-only change to CLAUDE.md; no generated content touched.

@netlify

netlify Bot commented Aug 10, 2026

Copy link
Copy Markdown

Deploy Preview for viam-docs ready!

Name Link
🔨 Latest commit 38249d8
🔍 Latest deploy log https://app.netlify.com/projects/viam-docs/deploys/6a79ec0e1c07470008153c62
😎 Deploy Preview https://deploy-preview-5259--viam-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 37 (🔴 down 1 from production)
Accessibility: 100 (no change from production)
Best Practices: 100 (no change from production)
SEO: 92 (no change from production)
PWA: 60 (no change from production)
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

@viambot viambot added the safe to build This pull request is marked safe to build from a trusted zone label Aug 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

safe to build This pull request is marked safe to build from a trusted zone

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants