Hey folks, I've run into what I suspect may be a bug. I have a grpc service which responds with a message that has a single boolean field (proto has more fields, but those are not populated by this service). Whenever the server responds with

false

in that field (i can adjust the state in the test), I'm getting this error from the protobuf plugin:

1) Verifying a pact between <consumer> and <provider> - <message>
2024-01-25 17:53:27.1661  ┃     1.1) has a matching body
2024-01-25 17:53:27.1661  ┃            $ -> Expected message '<message>' but was missing or empty

This happens regardless of whether consumer expects true or false. The server seems to respond with a correct message, seeing how changing the state to return

true

makes the plugin work correctly, passing if the consumer requested true and failing if the consumer requested false. This could be because boolean false is default, so the plugin cannot distinguish empty response from the explicit false, or am I misreading this?

Oh, it's probably because false is the default, Protobuf is dropping the field from the payload. It does the same thing with enums.