config Don't Bail If Optional Property Is Nullified

@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

Oct 30 '17 16:10 karthicks

Is there anything left to do on this?

Dec 18 '17 11:12 LavaToaster

@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

Feb 16 '18 11:02 karthicks

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

May 01 '18 04:05 karthicks

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!

Jan 20 '19 18:01 jjzazuet

Thanks for pulling this into the next release.

Jul 03 '19 22:07 karthicks

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

Jul 06 '23 08:07 ennru