Skip to content

Rename AlgorithmExperiment to ExperimentOption - #11

Merged
ps2 merged 1 commit into
mainfrom
rename/experiment-option
Oct 24, 2026
Merged

ps2 merged 1 commit into
mainfrom
rename/experiment-option

Conversation

@ps2

@ps2 ps2 commented Oct 24, 2026

Copy link
Copy Markdown
Contributor

Follow-up to #10. LoopKit already declares a public AlgorithmExperiment (the record stored with dosing decisions and uploaded to Tidepool and Nightscout), so any file importing both LoopKit and LoopAlgorithm got "'AlgorithmExperiment' is ambiguous". Qualifying doesn't help on this side, because LoopAlgorithm.AlgorithmExperiment resolves to the LoopAlgorithm struct.

Type rename only; raw values and encoded fixtures are unchanged. swift test passes (179).

Used by LoopKit/Loop#2608.

LoopKit declares a public AlgorithmExperiment (the record stored with dosing decisions), so files importing both modules could not use either name unqualified, and LoopAlgorithm.AlgorithmExperiment resolves to the LoopAlgorithm struct. Encoded fixtures are unchanged: they store the raw values.
@ps2
ps2 merged commit 273fcfe into main Oct 24, 2026
@ps2
ps2 deleted the rename/experiment-option branch October 24, 2026 18:46
AndEliRich pushed a commit to AndEliRich/LoopWorkspace that referenced this pull request Oct 24, 2026
…t, welcome screen width

- LoopAlgorithm: optional algorithm experiments (LoopKit/LoopAlgorithm#10), type renamed to ExperimentOption (LoopKit/LoopAlgorithm#11)
- Loop: use LoopAlgorithm's experiments, and add Guard + Runway (LoopKit/Loop#2608)
- LoopOnboarding: limit the welcome screen to a readable width (LoopKit/LoopOnboarding#39)
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