Repository navigation
Client control: QR pairing, roles, hardened mode, own Nightscout token - #2638
Merged
Merged
Conversation
…nd the client's own Nightscout token
♻️ Preview destroyed
🤖 Powered by surge-preview |
|||||||||
…me from the master
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.

Documents the new client control features of AAPS 4.
Wait with the merge until the matching code is in AndroidAPS
dev.What changes:
Screenshots still to add are marked with
SCREENSHOT NEEDEDcomments in the pages (the new add-client dialog, the client list with roles, the client wizard step). The QR code screen cannot be captured: AAPS blocks screenshots there.utils/qualitycheck.py --lang ENpasses.