We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Sometimes happen that the same config name is found multiple time in the same config source.
For instance :
quarkus.bannner.enabled=false quarkus.bannner.enabled=true
Or
quarkus: banner: enabled: false banner: enabled: true
In our quarkus projects (whose configuration is based on smallrye-config) this is just silently ignored.
I know that IDE helps avoiding it and developers should be disciplined when writing configuration, but in our large teams sometimes this happened.
But for a Developer Joy approach, it could be helpful to have an Out Of The Box solution.
For instance we could enable duplicate keys check with a system property like ?
smallrye.config.forbidDuplicateKeys
The text was updated successfully, but these errors were encountered:
fugerit79
No branches or pull requests
Sometimes happen that the same config name is found multiple time in the same config source.
For instance :
Or
In our quarkus projects (whose configuration is based on smallrye-config) this is just silently ignored.
I know that IDE helps avoiding it and developers should be disciplined when writing configuration, but in our large teams sometimes this happened.
But for a Developer Joy approach, it could be helpful to have an Out Of The Box solution.
For instance we could enable duplicate keys check with a system property like ?
The text was updated successfully, but these errors were encountered: