Skip to content

Remove the Nightscout-based remote command path#618

Open
bjorkert wants to merge 1 commit intodevfrom
cleanup/remove-nightscout-remote
Open

Remove the Nightscout-based remote command path#618
bjorkert wants to merge 1 commit intodevfrom
cleanup/remove-nightscout-remote

Conversation

@bjorkert
Copy link
Copy Markdown
Member

Summary

  • Trio dev's APNS-based remote command support has merged to main, so the Nightscout treatment-posting variant of remote commands is no longer needed.
  • Drops the .nightscout case from RemoteType, deletes TrioNightscoutRemoteView.swift, TrioNightscoutRemoteController.swift, and the now-orphaned NoRemoteView.swift fallback, and removes every .nightscout switch arm in remote settings, import/export, and device validation paths.
  • Storage keys are reused by the TRC and Loop APNS variants and remain untouched — no schema changes.

Migration

Existing users with remoteType previously set to "Nightscout" automatically fall back to .none on next launch: StorageValue's JSONDecoder fails on the removed enum case and returns the default value. No explicit migration step is needed.

Trio dev's APNS-based remote command support has merged to main, so the
Nightscout treatment-posting variant of remote commands is no longer
needed. Drop the .nightscout case from RemoteType, the Nightscout
remote view and controller, the unused NoRemoteView fallback, and all
.nightscout switch arms in the remote settings, import/export, and
device validation paths. Storage keys are reused by the TRC and
LoopAPNS variants and remain untouched.

Existing users with remoteType set to "Nightscout" automatically fall
back to .none on next launch: StorageValue's JSONDecoder fails on the
removed enum case and returns the default value.
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