Skip to content

Use only settings file, not envars #11

Description

@supremebeing7

There's a weird mix of using envars and settings.yml file for user inputs, where it saves the input to an envar, then writes it to the settings file. When reading, it fetches the yml file values and writes them to envars. All of the classes use envars instead of pulling directly from the settings file.

Essentially, there's no point in using envars when we could easily just use the settings file, and read from/write to it directly. Probably by defining a Settings class for easier fetching/writing.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions