When the format of an environment variable is invalid, we have a message like this: Environment variables with invalid format: EMAIL_TO_DEFAULT. It would be better to list the issues with the expected format from the .sample file, like:
Environment variables with invalid format:
- EMAIL_TO_DEFAULT: value "some-string-with-issue" expected to match "email" format
- ANOTHER_ENV: value "......." expected to match "url" format
- etc...
Problem:
Currently, when something fails, we know the env variable with the problem, but we have to find the problem (sometimes it might not be obvious when doing more complex stuff like regexs or if the value is not what we thought)
Branch/Commit:
Main branch / v 1.2.0
Describe the feature:
When the format of an environment variable is invalid, we have a message like this:
Environment variables with invalid format: EMAIL_TO_DEFAULT. It would be better to list the issues with the expected format from the .sample file, like:Problem:
Currently, when something fails, we know the env variable with the problem, but we have to find the problem (sometimes it might not be obvious when doing more complex stuff like regexs or if the value is not what we thought)
I will abide by the code of conduct