Based on this discussion
Note that this is a breaking change, even though unlikely, someone might be relying on the error of an undefined parser.
I think it is a nicer default behaviour though. And the previous behaviour is easy to reproduce by passing a z.undefined(). We can add this note on the release.
Based on this discussion Note that this is a breaking change, even though unlikely, someone might be relying on the error of an undefined parser.
I think it is a nicer default behaviour though. And the previous behaviour is easy to reproduce by passing a
z.undefined()
. We can add this note on the release.