Flag manually added data on CalorieHistory & HealthHistory #335
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.
This improvement allows methods related to the
HeathHistory
module andCalorieHistory
module to return a key calledwasManuallyEntered
for each data point received. This tells us if the user has added that data directly in Google Fit ( in which casewasManuallyEntered: true
), or if it was recorded with a sensor by a watch, band etc ( in which casewasManuallyEntered: false
). This is beneficial for cases when you need to get the actual data ( if you give rewards on workouts or you use it for some sort of competition ).The methods that will benefit from this are:
getDailyCalorieSamples
,getHeartRateSamples
,getBloodPressureSamples
,getBodyTemperatureSamples
,getOxygenSaturationSamples
,getBloodGlucoseSamples
.A similar issue was reported in #39 , though it's old.