You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Arc App has various extensions in its TimelineItem subclasses for fetching data from HealthKit. There's no reason why these can't be moved to LocoKit.
They should be wrapped in HealthKit module availability tests. But otherwise they should mostly be easily moved upstream from Arc App's ArcPath and ArcVisit subclasses and into the main Path and Visit classes. (Or more likely directly into the base TimelineItem class, given that they currently live in an ArcTimelineItem protocol).
Would probably also need to move over Arc App's HealthKit wrapper class, for simplified data fetching.
HKQuantityTypes
stepCount
activeEnergyBurned
heartRate (average value for the timeline item, and max value for the timeline item)
HKObjectTypes
sleepAnalysis
workoutType
It should also be easily extensible to support fetching of more HK types in custom subclasses, etc.
The text was updated successfully, but these errors were encountered:
Arc App has various extensions in its TimelineItem subclasses for fetching data from HealthKit. There's no reason why these can't be moved to LocoKit.
They should be wrapped in HealthKit module availability tests. But otherwise they should mostly be easily moved upstream from Arc App's
ArcPath
andArcVisit
subclasses and into the mainPath
andVisit
classes. (Or more likely directly into the baseTimelineItem
class, given that they currently live in anArcTimelineItem
protocol).Would probably also need to move over Arc App's HealthKit wrapper class, for simplified data fetching.
HKQuantityTypes
stepCount
activeEnergyBurned
heartRate
(average value for the timeline item, and max value for the timeline item)HKObjectTypes
sleepAnalysis
workoutType
It should also be easily extensible to support fetching of more HK types in custom subclasses, etc.
The text was updated successfully, but these errors were encountered: