fix: null value not persisted for properties of type JSON, Any, or Ob…

[siimsams]

Fix the following issue on latest master.

fixes #1895

Checklist

• Sign off your commits with DCO (Developer Certificate of Origin)
• npm test passes on your machine
• New tests added or existing tests modified to cover all changes
• Code conforms with the style guide
• Commit messages are following our guidelines

[siimsams]

I have added tests aswell. Please let me know if there is anything missing here. I'd really like to get this merged as we have many projects with this issue.

[ewrayjohnson]

@siimsams: Thanks. Although I proposed the fix, I had not found the time to create the tests.

[siimsams]

@siimsams: Thanks. Although I proposed the fix, I had not found the time to create the tests.

Thank you for proposing the fix. I added the tests aswell. Hope this gets approved and merged. We want to use latest versions but this issue blocks us from doing that.

"message": "invalid input syntax for type integer: "null"",
"stack":
error: invalid input syntax for type integer: "null"

[dhmlau]

@siimsams, thanks for your contribution. Please see my comments. I'll take a closer look at the change later today. Thanks.

[siimsams]

@siimsams, thanks for your contribution. Please see my comments. I'll take a closer look at the change later today. Thanks.

Thank you for such fast response! I have fixed the issues.

[coveralls]

Pull Request Test Coverage Report for Build 5324909921

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 4 of 4 (100.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.1%) to 84.814%

---

Totals
Change from base Build 5308588606:	0.1%
Covered Lines:	7267
Relevant Lines:	8264

---

💛 - Coveralls

[siimsams]

Fixed the commit message. It would be nice to have these required prefixes detailed in the pr/commit guidelines. As i could not have known about the requirement beforehand.

[dhmlau]

@siimsams, there's still error from the commit linter

   type must be one of [build, chore, ci, docs, feat, fix, perf, refactor, revert, style, test] [type-enum]

I suggest to squash the commit and have the commit message something like what you have in the title (make sure it's within 50 characters).

[dhmlau]

Your changes LGTM. Let's get the commit linting error fixed and we can go ahead to merge. Thanks.

[siimsams]

Squashed everything. Should be good to go now.

Your changes LGTM. Let's get the commit linting error fixed and we can go ahead to merge. Thanks.

Edit:
Looks like everything passed. LGTM!

[dhmlau]

@siimsams, thanks for your contribution. Your PR has landed! 🎉

[siimsams]

Thank you so much!