As a user, I want to have confidence in the params I am inheriting from IF and also freedom to override them as needed.
Rationale
We implemented some params logic in the original IF that has not been carried over into the refactor. Specifically, the ability to add params via the manifest file or to provide a params file on the command line.
Implementation details
Replicate the params logic from the original IF. Also add checks in IF that all params are listed in the canonical set.
Priority
4/5
Scope
tbc - could affect several core IF features
Size
1 day
What does "done" look like?
Refactored IF behaves similarly to original IF in terms of params logic
Does this require updates to documentation or other materials??
Story
As a user, I want to have confidence in the params I am inheriting from IF and also freedom to override them as needed.
Rationale
We implemented some params logic in the original IF that has not been carried over into the refactor. Specifically, the ability to add params via the manifest file or to provide a params file on the command line.
Implementation details
Replicate the params logic from the original IF. Also add checks in IF that all params are listed in the canonical set.
Priority
4/5
Scope
tbc - could affect several core IF features
Size
1 day
What does "done" look like?
Refactored IF behaves similarly to original IF in terms of params logic
Does this require updates to documentation or other materials??
Probably not, but tbc
What testing is required?
manual testing
Is this a known/expected update?
Expected in sprint 7