-
Notifications
You must be signed in to change notification settings - Fork 41.2k
Improve diagnostics for configuration properties binding failures #3778
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
👍 |
I'd argue that those two deliverables are "must haves". |
A proposal for this is available here /cc @philwebb |
The key part to the proposal is a custom It would be quite a bit nicer if Something like this in
I could then override this in
|
@wilkinsona & @snicoll, thanks for taking the initiative to get this sorted out so quickly! 😄 |
The extension point has been added. |
When configuration properties binding fails (for example due to an unknown field or a value that cannot be coerced), the error that you're greeted with isn't very friendly:
In order of importance, I'd like to see the following:
The text was updated successfully, but these errors were encountered: