Skip to content

Document GetStatus across component and service APIs#5184

Open
btshrewsbury-viam wants to merge 3 commits into
mainfrom
docs/api-getstatus
Open

Document GetStatus across component and service APIs#5184
btshrewsbury-viam wants to merge 3 commits into
mainfrom
docs/api-getstatus

Conversation

@btshrewsbury-viam

Copy link
Copy Markdown
Collaborator

What this adds

The Python, TypeScript, and Flutter SDKs expose a resource-level GetStatus method (backed by the common GetStatus RPC in viamrobotics/api) on every component and most services. It was undocumented: no rows in sdk_protos_map.csv, so it never appeared in the API reference — and it accounted for ~70 of the 119 warnings keeping the weekly SDK method coverage job red (#5142).

This PR adds a GetStatus section to all 18 component API pages and 8 service API pages (data manager, discovery, generic service, ML model, motion, SLAM, vision, world state store).

How

  • One GetStatus CSV row per resource, filling only the SDK columns the coverage scraper actually finds: Python get_status and TypeScript getStatus broadly; Flutter getStatus where Flutter supports the resource (no encoder, input controller, switch); the Go SDK has no per-resource GetStatus, so the Go column stays empty. Micro-RDK column set to No where the resource's section uses Yes/No (micro-rdk has no per-resource GetStatus RPC).
  • One proto description override file per resource (<resource>.GetStatus.md).
  • Regenerated the affected component/service markdown with update_sdk_methods.py. The regeneration also picks up drift since the last regen — mostly the /reference//dev/reference/ link migration in tables and minor upstream SDK docs wording — which is why the table diffs touch every row.
  • One generator tweak: ignore the proto-cased GetStatus duplicate the Python scraper picks up from the world_state_store page, exactly matching the existing ignore entries for that page's other duplicates (ListUUIDs, GetTransform, StreamTransformChanges, DoCommand).

Verification

Ran the full coverage script locally on this branch: the ~70 GetStatus warnings are gone (119 → 49 total), no missing-override warnings, and the generated sections render Python/TypeScript/Flutter tabs with scraped signatures and examples.

Part of a series addressing the #5142 warning backlog; companion PRs document the remaining component, robot, and app methods.

Refs #5142

The Python, TypeScript, and Flutter SDKs expose a resource-level
GetStatus method (backed by the common GetStatus RPC) on every
component and most services, but it had no rows in sdk_protos_map.csv,
so the API reference never mentioned it and the weekly SDK method
coverage job flagged ~70 unused-method warnings.

Add a GetStatus row for each of the 18 components and 8 services,
filling only the SDK columns the coverage scraper actually finds
(the Go SDK has no per-resource GetStatus; Flutter lacks encoder,
input controller, and switch). Add a proto description override file
per resource, and regenerate the affected component and service
markdown.

Also ignore the capitalized 'GetStatus' the Python scraper picks up
from the world_state_store page, matching the existing entries for
that page's other proto-cased duplicates (ListUUIDs, GetTransform).

Refs #5142.
@netlify

netlify Bot commented Jul 13, 2026

Copy link
Copy Markdown

Deploy Preview for viam-docs ready!

Name Link
🔨 Latest commit e19693c
🔍 Latest deploy log https://app.netlify.com/projects/viam-docs/deploys/6a550f1fc25fcb00072f60f9
😎 Deploy Preview https://deploy-preview-5184--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: 33 (🔴 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.

The first-sentence extractor for method-table descriptions only
stripped percent-style ({{% alert %}}) shortcode blocks. The
motion.MoveOnMap.md override starts with an angle-bracket
({{< alert >}}) block, so regenerating leaked an unclosed shortcode
opener into motion-table.md and broke the Hugo build. Strip
angle-bracket blocks the same way, non-greedily so a description
between two blocks survives.
…ence/apis

The docs restructure moved the API reference pages from
/dev/reference/apis/* to /reference/apis/*, leaving /dev/reference as
meta-refresh alias stubs. The generator still hardcoded the old
prefix, so the previous regeneration pointed every method-table link
at a stub page and htmltest failed. Update the anchor prefixes and
regenerate the files in this PR's scope.
btshrewsbury-viam added a commit that referenced this pull request Jul 13, 2026
Two CI fixes for the robot API regeneration:

- The docs restructure moved the API reference from /dev/reference/apis
  to /reference/apis, but the generator still hardcoded the old prefix,
  so the regenerated table links pointed at alias stubs and htmltest
  failed. Update the prefixes (same fix as #5184) and regenerate.
- The scraped transform_pcd parameter descriptions from the Python SDK
  contain 'i.e.', which the vale style rules reject. Add parameter
  description override files with equivalent wording.
@btshrewsbury-viam

Copy link
Copy Markdown
Collaborator Author

Merge order: merge this PR first. #5186 and #5187 are stacked on this branch (they share regenerated files); GitHub retargets them to main automatically once this merges. #5185 is independent.

Issue linkage: refs #5142 but does not close it — after all four PRs merge, ~24 warnings remain (tracked in #5188, #5189, #5190), so the weekly SDK method coverage job stays red until those get confirm-and-ignore entries. This PR also carries the two generator fixes the other PRs rely on: the /dev/reference→/reference anchor prefixes and the angle-bracket alert strip for table descriptions.


Generated by Claude Code

@btshrewsbury-viam

Copy link
Copy Markdown
Collaborator Author

Ethan (@stuqdog) would you mind reviewing this PR please? It covers the getStatus changes for most of the auto generated apis

@ale7714

Copy link
Copy Markdown
Member

Assigning Naveed because Ethan will be out for the next 8 weeks

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.

4 participants