Skip to content

Don't Bail If Optional Property Is Nullified#522

Closed
karthicks wants to merge 4 commits intolightbend:mainfrom
karthicks:issue-440
Closed

Don't Bail If Optional Property Is Nullified#522
karthicks wants to merge 4 commits intolightbend:mainfrom
karthicks:issue-440

Conversation

@karthicks
Copy link
Copy Markdown

@karthicks karthicks commented Oct 30, 2017

@havocp ,

This is a continuation of an earlier pull request, which got closed accidentally. I addressed the last comment you had in there here.

For details on the problem description, please refer to #440.

Regards,
Karthick

@LavaToaster
Copy link
Copy Markdown

Is there anything left to do on this?

@karthicks
Copy link
Copy Markdown
Author

@Lavoaster ,

No, there is nothing left to do on this. This is good to go. To reiterate, if one were to set an optional property to null, then with this change, a "false negative" exception will not be raised (see #440 for more details).

-Karthick

@karthicks
Copy link
Copy Markdown
Author

Can we make this a candidate for the next release, if possible?

@jjzazuet
Copy link
Copy Markdown

Hi. I'm also trying to figure out a way to omit specific bean properties from bean definitions in Kotlin. Any plans to merge this PR in? Thanks!

@karthicks
Copy link
Copy Markdown
Author

Thanks for pulling this into the next release.

Base automatically changed from master to main March 19, 2021 19:32
@ennru
Copy link
Copy Markdown
Member

ennru commented Jul 6, 2023

We do not intend to extend the functionality of "Typesafe Config" further.
See https://github.com/lightbend/config#maintained-by

@ennru ennru closed this Jul 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants