Skip to content

Conversation

@js3110
Copy link
Collaborator

@js3110 js3110 commented Jan 15, 2026

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

  • settings file yaml form
  • settings uploaded and applied as before

How to test

Try different settings, export and upload and test that it works.

Contributor checklist

  • Code passes lintr checks
  • Code passes all unit tests
  • New logic covered by unit tests
  • New logic is documented
  • App or package changes are reflected in NEWS
  • Package version is incremented

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

@js3110 js3110 changed the base branch from main to 719-enhancement-integrate-settings-upload-button-with-data-upload January 15, 2026 14:27
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.

Enhancement: Move from .rds to yaml file for settings

2 participants