I dislike the "warn on bad config" approach because I feel like often times when you have a misspelling or something in the configuration file, it is actively A Real Problem that could affect your deployment and the deploy should not be allowed to proceed.
I do however agree that more helpful error messaging is super useful, so I left the InvalidConfig module in place - just changed it to raise an exception.
I dislike the "warn on bad config" approach because I feel like often times when you have a misspelling or something in the configuration file, it is actively A Real Problem that could affect your deployment and the deploy should not be allowed to proceed.
I do however agree that more helpful error messaging is super useful, so I left the
InvalidConfigmodule in place - just changed it to raise an exception.