Joey Bleau
Joey Bleau
I will be attempting to fix this on my own and will report back with a patch and a PR if you'd like. Thanks for the great tool. All the...
Just adding a quick note that this scenario also triggers the same issue: `{"outter":[{"foo":{"bar": null}}, {"foo":{"bar":"test"}},{"foo":{"bar":null}}]}` I implemented a fix for the original case (in my first post) by modifying...
I'm tempted, for my purposes, to just ignore nulls when encountered and not to map them to a type at all. Leaving the office now so I'll update one final...
Additional case that breaks: ``` { "foo": [ { "bar": [{"baz":null}] }, { "bar": [{"baz":[{"bat": null}]}] }, { "bar": [{"baz":[{"bat": "hello"}]}] } ] } ``` I have fixed the scenarios...
Found one final additional scenario where, due to my change before, if the order so happens that we encounter a member of a type that is an ApexClass, but later...
**DO NOT MERGE.** Integration/regression tests pending, opened for review and discussion.
No worries! I want to spend more time with it. I started feeling a bit guilty to be honest that I sort of dumped all of this out of nowhere...