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

Empty values are always treated as non-present #114

Merged
merged 2 commits into from
May 13, 2019

Conversation

dmlloyd
Copy link
Contributor

@dmlloyd dmlloyd commented May 13, 2019

Fixes #83 (for real)

@dmlloyd
Copy link
Contributor Author

dmlloyd commented May 13, 2019

This is a draft PR because it does not pass TCK due to eclipse/microprofile-config#407

@kenfinnigan
Copy link
Contributor

Depending on what happens with the spec, we can "exclude" the failing test(s) so the build passes if we need it released.

It's safe to exclude on the premise we're challenging the TCK

@dmlloyd dmlloyd marked this pull request as ready for review May 13, 2019 15:39
@dmlloyd
Copy link
Contributor Author

dmlloyd commented May 13, 2019

OK I've disabled the offending TCK tests.

@jmesnil
Copy link
Contributor

jmesnil commented May 13, 2019

Let's merge this and discuss the spec behaviour in eclipse/microprofile-config#407

@kenfinnigan kenfinnigan merged commit cf2ead7 into smallrye:master May 13, 2019
@kenfinnigan
Copy link
Contributor

Do we need another release?

@dmlloyd dmlloyd deleted the 83-again branch May 13, 2019 17:56
@dmlloyd
Copy link
Contributor Author

dmlloyd commented May 13, 2019

Yes please

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Inconsistent behaviour between Config.getValue() and Config.getOptionalValue()
3 participants