This PR closes #3 by adding better management of temperatures on the frontend.
PR Changes:
Adding a route/page to view and manage the temperatures through a table which they can delete the corresponding measurement
Migrate endpoints that targeted specific temperatures by id from the device specific to a shallower temperature route i.e. /devices/:deviceId/temperatures/:temperatureId -> /temperatures/:temperatureId.
A GET /temperatures endpoint which currently retrieves all temperatures in most recent order (i.e. latest temperature first in the array of the response)
Originally, the related issue planned for time range filtering but this has been excluded as it would be appropriate to implement pagination functionality (see #4 ) first which then dictates how the filtering feature works.
This PR closes #3 by adding better management of temperatures on the frontend.
PR Changes:
/devices/:deviceId/temperatures/:temperatureId -> /temperatures/:temperatureId.GET /temperaturesendpoint which currently retrieves all temperatures in most recent order (i.e. latest temperature first in the array of the response)Originally, the related issue planned for time range filtering but this has been excluded as it would be appropriate to implement pagination functionality (see #4 ) first which then dictates how the filtering feature works.
Feature Screenshot: