Skip to content

Log g5 errors, non-ok calibration states, and unknown data#487

Merged
ps2 merged 2 commits intodevfrom
g5-errors
Jun 25, 2017
Merged

Log g5 errors, non-ok calibration states, and unknown data#487
ps2 merged 2 commits intodevfrom
g5-errors

Conversation

@ps2
Copy link
Collaborator

@ps2 ps2 commented May 27, 2017

No description provided.

@ps2 ps2 merged commit 76762ed into dev Jun 25, 2017
@ps2 ps2 deleted the g5-errors branch July 1, 2017 18:57
ps2 pushed a commit that referenced this pull request Jan 10, 2022
…t.isCritical` (#487)

* LOOP-3973: Introducing `interruptionLevel` as a replacement for `Alert.isCritical`

This introduces the notion of three Alert "interruption levels" similar to iOS's
UNNotificationInterruptionLevel (https://developer.apple.com/documentation/usernotifications/unnotificationinterruptionlevel)
as a replacement of the `isCritical` flag.

https://tidepool.atlassian.net/browse/LOOP-3973

* Revert change accidentally pushed (that would make iOS critical alerts show up while app is in foreground)

* LOOP-3974: Make Bluetooth Off a critical alert

* Remove `interruptionLevel` from CoreData altogether.

It used to be a "convenience" to have the `isCritical` boolean there, but because `interruptionLevel` is really part of `Alert.Content` (and is serialized in the `foregroundContent` and `backgroundContent` fields already), I think keeping this field is  at best confusing and at worst misleading.

* Hoists interruptionLevel into Alert

* Fix primitiveInterruptionLevel

* Adds unit test to insure confidence in `interruptionLevel` getter/setter

* PR Feedback
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

Comments