Skip to content

Enforce default values for Configs #3395

Description

@lomky

Thanks for creating an issue! Please fill out this form so we can be sure to have all the information we need, and to minimize back and forth.

  • What are we trying to do?
    Config value typos can lead to problems of all sizes. Let's make it required they have a default value or throw a fit.

  • What feature or behavior is this required for?
    App stablity

  • How could we solve this issue? (Not knowing is okay!)
    Application error in the Config model if we haven't coded a valid DEFAULT.

  • Anything else?
    Very important typo #3394 Bugfix: Standardize shared_reset_days key #3393

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions