influxdata / influxdata/iot-api-js
`pages/api/measurements/index.js` is listed as a “Telemetry query endpoint”, but it doesn’t export a default Next.js API handler (it exports `getMeasurements()`), so it isn’t directly an endpoint. Consider rewording this as a shared telemetry query helper, or add an actual `/api/measurements` route if that’s intended.
- Dominant language
- JavaScript
- Stars
- 12
- Forks
- 5
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 2
Description
`pages/api/measurements/index.js` is listed as a “Telemetry query endpoint”, but it doesn’t export a default Next.js API handler (it exports `getMeasurements()`), so it isn’t directly an endpoint. Consider rewording this as a shared telemetry query helper, or add an actual `/api/measurements` route if that’s intended.
```suggestion
| `pages/api/measurements/index.js` | Shared telemetry query helper |
```
_Originally posted by @Copilot in https://github.com/influxdata/iot-api-js/pull/29#discussion_r2789216102_
Contributor guide
No contributing guide indexed for this repository
Research direction
Review pages/api/measurements/index.js and its getMeasurements() export, then check the documentation table entry described in the issue. Done means the entry accurately identifies this as a shared telemetry query helper, or an actual /api/measurements route is added if that intent is confirmed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nextjs
- Domain
- api
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100