-
Notifications
You must be signed in to change notification settings - Fork 115
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
Default values even outside of CDI #533
Comments
In order to have a single, consistent view of default values, all default values should be established once (ideally when the configuration is being built). This can be done programmatically, or via the CDI mechanism, or by a mixture of both: the important thing is that the default value for a given property can only be defined one time. The comment on #559 talks about adding a method to the accessor which allows a default value to be given at resolution time, which completely undermines the principle of having fixed default values. |
Description
Sometimes a property needs to have a value that is returned if no configuration source has explicitly defined what the value of the property should be. This is commonly referred to as a "default value".
As a:
...I need to be able to:
...which enables me to:
Have a similar experience between CDI and the programmatic API; have a consistent result even if I switch between APIs.
Related to #475.
The text was updated successfully, but these errors were encountered: