Closed adnelson closed 2 years ago
I'm not sure why the CI failed, it looks like some of the jobs weren't run. If there's anything further you need from me on this PR please let me know.
Hi @adnelson. Thanks for the PR.
Not sure why CI failed, I'll have to take a look at that.
This change seems reasonable, I'm curious though if the [@decco.default]
annotation would meet your use case?
@ryb73 thanks for the response, I tried it but unfortunately I get an error if the field is set to undefined
. It finds the key set on the object, then tries to parse it as null
, which fails, since null !== undefined
Just wondering is this ok to merge? Does the reasoning make sense?
❓
Hey @adnelson, sorry for the delay. I merged the PR but am unable to publish. You can see #82 for more info.
This change has been released in v1.6.0.
Changes decco's
optionFromJson
so that it treats bothnull
andundefined
asNone
. This makes it much easier to deal with objects coming in from JS code which might useundefined
or have the field missing entirely.