gluco-check
gluco-check copied to clipboard
Replace /api/v1/entries/current with /pebble
-
I'm submitting a ... Refactoring request
-
What is the current behavior? To find someone's bloodsugar, Gluco Check queries the endpoint: /api/v1/entries/current
If we were to replace this with a call to /pebble, we could potentially get the same information,
while also reducing the number of API calls needed if the user has also requested IOB/COB. -
What is the motivation / use case for changing the behavior? Eliminating an API call would speed up the response time
-
Other information that could help us solve this issue: Not yet sure if /pebble provides all the required info. This must be validated before switching can be considered