v1.2.0 #336
Merged
v1.2.0 #336
Conversation
This file contains 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
Collaborator
ps2
commented
Dec 24, 2016
ps2
commented
- Support for battery levels on x22 pumps
- Italian translation
- Lock screen widget
- Algorithm change: If BG is < 55 then temp to 0, even if eventualBG is above or in range.
- Added Battery Chemistry Selection in SettingsTableViewController - Add User Var to store the Battery Chemistry Setting - Added defaults and Enum for Battery Chemistry Type
- Added Battery Calculation - Hide Setting for Battery Type on MySentry Pumps
- Updated Switch Descriptions and Alkaline syntax
Added "s" to http
Merge hotfix back into dev
…svt/Loop into jlucasvt-dev-1.1.1-x22BatteryStatus
…dating with shared code, misc refactoring
X22 battery pct
Adding Italian translations
Merge upstream/dev
Move GlucoseTrend model from WatchApp Extension into Loop.
Update rl frameworks to 0.12.9 to get alkaline battery chemistry changes
Apply "Missing Localizability" suggested XCode fix
Clicking Recommended copies values down! Closes #286
* Copy InsulinKit framework for DoseMathTests (otherwise it won't run) * Remove default value for allowPredictiveTempBelowRange Make this explicit to remove confusion since the only place where we rely on the default value is in our unit tests.
Update osx_image to xcode8.1 to get Swift 3.0.1
…ange. Simplify code by removing allowPredictiveTempBelowRange flag.
* Initial pass at creating a lock screen widget (aka. "Today Extension")
Changes to Loop:
1. Created a TodayExtensionDataManager which keeps an eye on DeviceDataManager
and stores data in TodayExtensionContext
2. Added Loop to a shared app group
Changes Loop TodayExtension:
1. New target
2. Reuses the HUD view from StatusTableViewController
3. Deserializes TodayExtensionContext data from share app group defaults
4. Displays basic data (currently only the current BG) in the lock view
* Use MAIN_APP_BUNDLE_IDENTIFIER instead of hardcoding com.loudnate
* Rename the widget to just "Loop" and remove the iOS 10.1 install requirement
* Add basal, reservoir and battery data to the today extension.
In addition, inject some debug data if we're running on a simulator so
that we can easily test the experience.
* Improve the way that TodayExtensionContext handles optional sections
* Clean up the UI
- wrap the StackView in a UIView
- set the dimensions properly
- fix all constraint issues
* Add support for net basal rates in the lock screen widget
Along the way, refactor the lastTempBasal visual calculations out
of StatusViewController and into LoopManager so that it can be shared
with TodayExtensionDataManager.
* Pass sensor info along to the extension.
This makes the alert icon do the right thing.
Do some refactors along the way to clean things up.
* Plumb the "eventual glucose" value through to a subtitle in the widget.
* Internationalize the eventual glucose string properly
* Clean up TodayExtensionContext innards
1. Move the store/retrieve semantics into a NSUserDefaults extension
2. Change TodayExtensionContext to implement RawRepresenable and generally
follow the semantics in WatchContext
3. Fixed all cases where we were storing non-conformant data, which
was resulting in serialization errors
related: fixed a minor bug in TodayViewController where we were not
calling completionHandler() reliably.
* Rename the widget and all references to 'Loop Status Extension'
* Update version number to 1.1.2 to match container.
* Rename scheme to match new extension name
* Remove boilerplate comments
* Remove vestigial lastContext code
* Change eventual glucose to be a double value instead of a string, and
plumb the preferred unit through the context as well.
* Squish a few small bugs in context data transfer and with preferred units.
* Correctly deserialize GlucoseTrend.
* Fix busted merge.
* Remove unnecessary imports and frameworks to minimize exposure to
frameworks that do not support application extensions (see #292)
* Change GlucoseHUDView.set() to stop taking GlucoseValue
This is in preparation for a future change where StatusExtensionContext
will stop having knowledge of GlucoseValue so that it can stop pulling
in the LoopKit framework, which is not extension-API-safe.
* Elminate all framework dependencies from Loop Status Extension
LoopKit and InsulinKit frameworks are not extension API safe. Switch
to using common data structures that don't reference those frameworks.
* Resolve blown merge.
* Add HKUnit extension to get preferredMinimumFractionDigits
That extension to HKUnit comes from LoopKit, which is no longer
included with the Loop Status Extension. Not sure how this compiled
without this fix in the past.
* Back out erroneous DEVELOPMENT_TEAM values.
* Fix API nit
* Rely on MAIN_APP_BUNDLE_IDENTIFIER
* Rename .shared to .appGroup and make it a class var (modeling .standard)
* Move NetBasal calculations into its own class
* Move the app group suite name into a per-target Bundle extension
In addition, add the MAIN_APP_BUNDLE_IDENTIFIER into the Info.plist
so that each target can access it.
* Refactor the Bundle.appGroupSuiteName extension code for clarity
Eliminate duplicate code where we're choosing the appropriate bundle
inside the extension; instead let the caller choose the right bundle
and have common code for .appGroupSuiteName.
* Switch to a struct; use let instead of var
* Make all context struct members constant
This requires a slight restructuring of the way we initialize
GlucoseContext so that we create the SensorDisplayable first
if it exists.
* Set the Loop Status Extension build to CURRENT_PROJECT_VERSION
If minBG is below 55, then shut off basal, even if eventualBG is in r…
Bump version to 1.2.0
…, and bumping status extension version up to 1.2.0
Update bundle identifier to com.loopkit
Pass the raw HKUnit.unitString (eg. mmol<180.1558800000541>/L) through the context, as opposed to the unitDisplayString which is uses the glucose-centric version (eg. mmol/L). This way we can properly hydrate the unit on the extension side and represent it in the extension. Fixes #311.
Properly support mmol/L in the status extension.
…tension adding CustomDebugStringConvertible support for status extension manager
Fix the sourceTree for the Loop Status Extension storyboard.
…tally allocated app group ids
Change how app group id is constructed to avoid conflict
ps2
pushed a commit
that referenced
this pull request
Nov 25, 2020
* changing dash to en-dash * localizing watch no glucose value representation
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.