Repository navigation
Import LoopKit instead of LoopAlgorithm - #47
Merged
Merged
Conversation
LoopKit owns the units and value types now.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Switches
import LoopAlgorithmtoimport LoopKit. LoopKit now ownsLoopQuantity,LoopUnitand the shared value types under the same names (LoopKit/LoopKit#674), and LoopAlgorithm's public API no longer exposes them (LoopKit/LoopAlgorithm#17).DeviceLogUploaderused LoopAlgorithm'sDate.dateFlooredToTimeInterval; it now has a file-private copy.This is one of the plugin changes listed in LoopKit/LoopAlgorithm#17's plan. It needs LoopKit/LoopKit#674 to build, and goes in with the LoopWorkspace bump that adopts it. Built in a full LoopWorkspace build with all plugins.