Skip to content

Fatty Scoped Config store #24

@stoopdapoop

Description

@stoopdapoop

Fatty should have a more centralized configuration store at a global, channel, and server scope. There should an overload heirarchy where more specific configs overwrite less specific ones. There should be an optional "force" attribute that can cause a lower priority value to forcibly overwrite a higher priority value.

These should be modifiable at runtime, unless explicitly marked. If marked then emit an error.

This store should have a common api should replace modules needing to manually work out what scope to check for configs. We should have every config value use this, but they should be defaulted to "Write only" by default. So we don't leak anything.

By default config values are not serialized if modified at runtime. Though maybe we should add a param to serialize them.

These config values should not be cached by modules.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions