Skip to content

Manage data: address Copilot follow-ups from PR 4901#4903

Merged
shannonbradshaw merged 1 commit intoviamrobotics:new-docs-sitefrom
shannonbradshaw:content/data-copilot-followup
Apr 10, 2026
Merged

Manage data: address Copilot follow-ups from PR 4901#4903
shannonbradshaw merged 1 commit intoviamrobotics:new-docs-sitefrom
shannonbradshaw:content/data-copilot-followup

Conversation

@shannonbradshaw
Copy link
Copy Markdown
Collaborator

Summary

Two small follow-up fixes to content that landed in #4901. Both were flagged by Copilot review on #4902 but apply to files that aren't in that PR's diff, so they need a separate PR.

  • query-data.md alert: the wording overstated things. It claimed every SQL example on the page includes the specific clause `AND time_received >= CAST('2000-01-01T00:00:00.000Z' AS TIMESTAMP)`, but the "filter by time range" example uses a different literal timestamp form (`time_received > '2025-01-15T00:00:00Z'`). Softened the alert to say "every SQL example includes an explicit lower bound on `time_received`" and kept the specific workaround clause as a concrete example in the troubleshooting advice.
  • data-management-tutorial.md "What just happened?" callout: referred to `test-sensor.Readings()`, but the rest of the page (and the Viam app's CONTROL panel — verified at `app/test-cards/src/lib/components/sensor-view.svelte:49`) uses `GetReadings`. Aligned to `GetReadings`.

Test plan

  • Netlify deploy preview builds
  • query-data.md preview: alert wording reads correctly
  • data-management-tutorial.md preview: "What just happened?" step 1 says `GetReadings()`

🤖 Generated with Claude Code

- query-data.md alert: the wording claimed every SQL example on the
  page uses the specific CAST clause, but the "filter by time range"
  example uses a different literal timestamp. Soften to "every SQL
  example includes an explicit lower bound on time_received" and
  move the specific workaround clause into the troubleshooting advice.
- data-management-tutorial.md: the "What just happened?" callout
  referred to test-sensor.Readings(), but the rest of the page and
  the Viam app CONTROL panel use GetReadings. Align to GetReadings.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@netlify
Copy link
Copy Markdown

netlify Bot commented Apr 10, 2026

Deploy Preview for viam-docs ready!

Name Link
🔨 Latest commit f8f94d9
🔍 Latest deploy log https://app.netlify.com/projects/viam-docs/deploys/69d9516c9d2b3d0008a15fe7
😎 Deploy Preview https://deploy-preview-4903--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: 39 (🔴 down 7 from production)
Accessibility: 99 (🔴 down 1 from production)
Best Practices: 92 (no change from production)
SEO: 89 (🔴 down 3 from production)
PWA: 60 (🔴 down 10 from production)
View the detailed breakdown and full score reports

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

@shannonbradshaw shannonbradshaw merged commit 6981a74 into viamrobotics:new-docs-site Apr 10, 2026
11 checks passed
@shannonbradshaw shannonbradshaw deleted the content/data-copilot-followup branch April 10, 2026 21:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant