Decoding Invalid Strings sometimes raise MatchError instead of Protobuf.DecodeError #339
Labels
Kind:Bug
A bug. Can be a documentation bug, Dialyzer issue, or anything that just "doesn't work".
Hello!
I found that in newer versions of the lib sometimes when you decode an invalid string, a
MatchError
is raised instead of aProtobuf.DecodeError
.Example:
![image](https://user-images.githubusercontent.com/25253248/213042838-ac154d5c-d4ce-4301-bae7-eaa6907dd587.png)
Specifically, I was testing when I tried to decode JSON strings. Seems like some strings still raise the appropriate
Protobuf.DecodeError
.Good Example:
![image](https://user-images.githubusercontent.com/25253248/213043487-7b90efcf-105d-4a77-a7fa-45da54f141a0.png)
I think it is related to the added functionality surrounding
__unknown_fields__
.Let me know if you have any questions or if there is anything I can do to help!
The text was updated successfully, but these errors were encountered: