Skip to content
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

@ConfigProperties doesn't handle unset primitives #13523

Closed
geoand opened this issue Nov 27, 2020 · 0 comments · Fixed by #13524
Closed

@ConfigProperties doesn't handle unset primitives #13523

geoand opened this issue Nov 27, 2020 · 0 comments · Fixed by #13524
Assignees
Labels
area/config kind/bug Something isn't working
Milestone

Comments

@geoand
Copy link
Contributor

geoand commented Nov 27, 2020

Describe the bug
When primitives are used in a class annotated with @ConfigProperties, then Quarkus fails at runtime if the primitive is not set.

Expected behavior
Unset primitives should not prevent Quarkus from starting and their value should just be the default set by the JVM

@geoand geoand added the kind/bug Something isn't working label Nov 27, 2020
@ghost ghost added the triage/needs-triage label Nov 27, 2020
@geoand geoand self-assigned this Nov 27, 2020
geoand added a commit to geoand/quarkus that referenced this issue Nov 27, 2020
geoand added a commit that referenced this issue Nov 27, 2020
Ensure that primitive types in @ConfigProperties work as expected
@ghost ghost added this to the 1.11 - master milestone Nov 27, 2020
@gsmet gsmet modified the milestones: 1.11 - master, 1.10.2.Final Nov 30, 2020
gsmet pushed a commit to gsmet/quarkus that referenced this issue Nov 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/config kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants