Hi,
thank you for the library. It really improved the way I approach configuration files.
Finally I have types and proper sections.
What I am missing is schema: I would love to be able to enforce that some parameters are obligatory, their type and provide a description, also raise an exception if there is some unknown parameter is configured.
I think I could use something like marshmallow

We are already able to customize the dictionary of messages simplelogin flashes. However, there is no easy way to:

1. Toggle messages on and off
2. Customize the categories of the flashes

Toggling could be useful if the user has implemented a custom login checker function, or if the user doesn't want to flash these messages. Custom categories could be useful for projects structured with diffe

Flask-Discord makes use of the Flask config for few configurations values like Discord application client ID, secret, etc. and more. However, the documentation is missing list and description about all of the keys used by the library.

Describing them in the documentation might be helpful to the library users to better fine tune it as for their needs.

Quick way to find them is to look for `co

There are different conventions for virtual environments.
Like creating all the virtual environments on a folder ( "~/virtualenvs/" ),
or naming the virtual environment with a leading dot ( ".../project/path/.venv" ),
right now the virtual environment is created inside the project folder with a default name "venv"

If a PEP is called on a function, and the policy denies its execution, there should be a parameter that allows to specify a return value and/or a function that returns such value.