nightscout / nightscout/AndroidAPS
Feature Request: additional feature for MAX Carbs
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 1.2k
- Forks
- 6.4k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 19
Description
Dear team,
I suggest to add to the “max allowed carbs” a feature, that would prevent my kid to bolus consecutiveley more than once and with the result that the max carbs entry of for example 70 carbs is not mandatory anymore. For the second carb entry within a defined time period the system should only store the carbs, but the calculator shouldn’t be considering it and deliver no insulin for it., like I would store the carbs in the carb tab with a time offset.
Thanks for considering this idea.
I hope this will be beneficial for at least DT1 parents :-)
AAPS 3.2.0.2
fullrelease
Reporting bugs
- Note the precise time the problem occurred and describe the circumstances and steps that caused
the problem - Note the Build version (found in the About dialog in the app, when pressing the three dots in the
upper-right corner). - Obtain the app's log files, which can be found on the phone in
/storage/emulated/0/Android/data/info.nightscout.androidaps/
See https://wiki.aaps.app/en/latest/Usage/Accessing-logfiles.html - Open an issue at https://github.com/nightscout/AndroidAPS/issues/new
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the MAX Carbs setting and the bolus calculator code in AndroidAPS, then review how consecutive carb entries are stored and evaluated. Confirm the intended time window and behavior for the second entry with maintainers. Done means the requested entries are stored while insulin is not calculated for qualifying follow-up entries, with tests covering the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100