Skip to content

Conversation

@erikdi
Copy link
Contributor

@erikdi erikdi commented Apr 26, 2018

Essentially handle Bolus recommendation the same as Basal recommendations. There is probably historic reasons why these are treated differently. Given that update() is always called before recommendBolus it does not make a lot of functional sense though.

This is in preparation of being able to automatically do bolus' out of LoopDataManager.

erikdi added 2 commits April 26, 2018 22:53
Make Bolus recommendation part of Loop update and don't allow
external calls to it.  The data doesn't change in any case and
update() is called in all places where we want a Bolus
recommendation.

This is in preparation of automated Bolus code, which needs
consistent Bolus and Basal data.
The recommendedBolus variable contains the same information.
@ps2 ps2 merged commit 140df85 into LoopKit:dev May 24, 2018
ps2 added a commit that referenced this pull request Oct 5, 2024
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.

2 participants