98 update configuration management to use confy for file based configuration #100

Merged
PatrykHegenberg merged 5 commits from 98-update-configuration-management-to-use-confy-for-file-based-configuration into main 2024-05-09 16:29:03 +02:00
PatrykHegenberg commented 2024-05-09 16:26:50 +02:00 (Migrated from github.com)

Description

The program logic has been changed so that the configuration is now read from a configuration file using confy. These are located under Linux in $XDG_HOME/.config/caesar

Motivation and Context

This serves to further modularize the program and to be able to use different white configurations later on. For example, the configuration is probably read and processed differently in the GUI app (desktop/Android) than in the CLI. This is now possible.

Closes #98

How Has This Been Tested?

manually tested

Screenshots / Logs (if applicable)

Types of Changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation (no code change)
  • Refactor (refactoring production code)
  • Other

Checklist:

  • My code follows the code style of this project.
  • I have updated the documentation accordingly.
  • I have formatted the code with rustfmt.
  • I checked the lints with clippy.
  • I have added tests to cover my changes.
  • All new and existing tests passed.
## Description The program logic has been changed so that the configuration is now read from a configuration file using confy. These are located under Linux in $XDG_HOME/.config/caesar ## Motivation and Context This serves to further modularize the program and to be able to use different white configurations later on. For example, the configuration is probably read and processed differently in the GUI app (desktop/Android) than in the CLI. This is now possible. Closes #98 ## How Has This Been Tested? manually tested ## Screenshots / Logs (if applicable) ## Types of Changes <!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Bug fix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [ ] Documentation (no code change) - [ ] Refactor (refactoring production code) - [ ] Other <!--- (provide information) --> ## Checklist: <!--- Go over all the following points, and put an `x` in all the boxes that apply. --> <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] My code follows the code style of this project. - [ ] I have updated the documentation accordingly. - [x] I have formatted the code with [rustfmt](https://github.com/rust-lang/rustfmt). - [x] I checked the lints with [clippy](https://github.com/rust-lang/rust-clippy). - [ ] I have added tests to cover my changes. - [x] All new and existing tests passed. <!--- Thank you for contributing! -->
Sign in to join this conversation.
No description provided.