Enhancement/Refactor: move settings from rds to .yaml #901
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue
Closes #892
Description
Settings file refactored to .yaml for better readability and user configuration.
This PR is the most basic implementation, directly changing the import and export from rds to yaml, but maintaining all other features. Later PRs can develop the yaml file to make it more user friendly (#900 and #891 )
Definition of Done
How to test
Try different settings, export and upload and test that it works.
Contributor checklist
Notes to reviewer
For this PR, I have implemented a Hard change from .rds to yaml. Not sure if that is the best approach though, as we may want to keep rds in case anyone has saved their settings previously... but eventually we will only need yaml