Closed bwetherfield closed 4 years ago
This one is now ready for your review, @MaxDesiatov ! Thanks
@bwetherfield I'm ready to review this again when conflicts are resolved 🙂
Thanks, @MaxDesiatov ! I also need to add back the missing test :) Will keep you posted
OK - should be ready for review! Thanks, @MaxDesiatov
My apologies, @MaxDesiatov - should be in now!
Prior to this fix, we found that decoding an empty string (represented as a null element),
<string/>
was confusing the decoder. I can't seem to find any issues logged. Perhaps @jsbean has an idea where these might be hiding...?I'm also building up to a PR that addresses the array-of-empty-elements issue, but I am trying to disentangle the changes we merged into a separate branch!