[Health] add delete by client id and fetch unit support #1223
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 pull request focuses on unit conversions, and record deletion capabilities. The changes improve the flexibility of data handling and add support for more granular operations on health records.
Unit Conversion:
HealthDataConverter
: Added support for unit conversions inWeightRecord
,HeightRecord
,BodyTemperatureRecord
, andBloodGlucoseRecord
by introducing adataUnit
parameter to theconvertRecord
method. This allows dynamic conversion based on specified units (e.g., kilograms to pounds, Celsius to Fahrenheit).Metadata:
HealthDataWriter
: Updated various methods (writeData
,writeWorkoutData
,writeBloodPressure
, andwriteMeal
) to include optionalclientRecordId
andclientRecordVersion
parameters in theMetadata
object. This facilitates better tracking and versioning of health records. [1] [2] [3]Record Deletion:
HealthDataOperations
: Introduced a newdeleteByClientRecordId
method to allow precise deletion of health records usingclientRecordId
anddataTypeKey
. This provides a more targeted approach to record management.Data Retrieval:
HealthDataReader
: Added support for specifying adataUnit
parameter during data retrieval, enabling unit-specific filtering and processing in thegetData
method. [1] [2]