Getting Data: add Node.js SDK query examples#91
Open
Freddyminu wants to merge 2 commits into
Open
Conversation
Collaborator
Author
|
@vitorfdl Not 100% if the best option was to add it to the existing getting data page, but I decided to do that instead of grouping it with the TagoIO SDK documentation or making a separate page just for it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Expands
getting-data.mdwith a full Node.js SDK section covering filters, date ranges, pagination, all query types, aggregations, and common pitfalls. Adds a link from the Node.js SDK page to the expanded doc.Why
The existing page was REST-only with no SDK examples. Power users were hitting support for things like aggregate queries, conditional filters, and pagination patterns that should be self-serve.
There was some back and forth on where to put this content. First pass was a standalone
devices/advanced-data-queries.mdpage, then it moved toanalysis/sdk/to sit alongside the Node.js and Python SDK docs. Both felt off — the new page was a fourth item next to the two SDK reference pages and didn't belong there, and a separate device page duplicated context that already lives ingetting-data.md. Merging into the existing page keeps device data queries in one place.Test plan
getting-data.mdwith both REST API and Node.js SDK sections visibleRisk (CIA)
Likelihood: ⚪ None | Impact: ⚪ None | Exposure: ⚪ None
Docs-only change, no behavior or API surface affected.
Closes #87