-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UW-500 - Allow forced conversion between formats #413
Comments
Marked as 'refactor' as this behavior was reasonably expected rather than necessarily 'new' |
Initial testing shows that YAML is already accepted, tested and documented as universally allowed input, so perhaps --force is not needed, only improved documentation |
After further re-checking requirements and testing, YAML as output has some issues in creating a valid YAML from sh/ini or nml dicts. This may again require --force to allow this behavior. |
Further discussion in group: we will allow YAML as output always, for much the same reason it is a valid input. However, this will be exclusive to YAML explicitly. |
Completed by #414 |
Description
User story: Can you use config realize to translate a config file from one format to another? E.g., I wanted to take an nml file and convert it to .yaml. Could I do that via uw config realize -i foo.nml --input-format nml -o foo.yaml --output-format yaml?
Requirements
YAML should always be accepted as input or output format. Documentation and tests must be updated appropriately
Acceptance Criteria (Definition of Done)
ability to convert supported formats to yaml format is restored
--force flag for overriding the check that allows YAML to convert to other file formats
documentation updated
tests updated
Additional context
Allowing YAML as always accepted supplemental file will be covered in UW-504
The text was updated successfully, but these errors were encountered: