Repository navigation
update LoopKit: share the Core Data model used by next-dev - #538
Merged
Merged
Conversation
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.
Purpose
Maintain parameters stored by next-dev but not by earlier version of Loop.
Overview
There are additional parameters stored in the next-dev data that are not found in earlier versions of Loop.
This PR enables those extra parameters to be preserved for users who transition from next-dev back to dev or main.
Although dev and main will not add entries to these extra parameters, the values added by next-dev are maintained and are available when the user returns to next-dev.
Examples
These are some of the extra parameters in next-dev: