-
Notifications
You must be signed in to change notification settings - Fork 4
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #423 from HopkinsIDD/hotfix/patching-abilities-doc…
…umentation * `flepimop patch` unit test for `seir::parameters` Added a unit test to demonstrate the issue described in #375 (comment) with respect to the `seir::parameters` section. Appears to be related to if the parameters are a list or a dict. * Fix `parse_config_files` TL key override behavior Corrected an issue where `parse_config_files` would try to merge top-level keys which comes from `confuse`. Work around is to manually build a dictionary and then convert that to a `Configuration` object. * Add `--indent` option to `flepimop patch` For configuration of the outputted yaml. * Add detailed example to `flepimop patch --help` * Force default indent of `flepimop patch` to 4 * Upgrade TL key collision from warning to error * modify approach to handling help * Add `_dump_formatted_yaml` for custom yaml dump Added an internal utility to custom format the yaml representation of a `confuse.Configuration` object. Creates a custom `yaml.Dumper` class that contains all of the custom representation changes as to not modify the `yaml` pkg defaults. * `flepimop patch --help` uses example configs Changed the help page to use existing files in the `examples/tutorials` directory rather than construction test configs on the fly per a suggestion by @pearsonca. * update multi-configs gitbook * `parse_config_files` error includes config name * Resolve seir/outcome modifier scenarios * `flepimop patch` documenation edits Stronger and clearer wording suggested by @saraloo. --------- Co-authored-by: Carl A. B. Pearson <[email protected]>
- Loading branch information
Showing
8 changed files
with
657 additions
and
51 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.