Updating Proto definitions on the server side breaks client

[majst01]

Describe the bug

We updated the proto definition of our API as such that one message contains a additional field like so:

before:

message A {
  string name = 1;
}

after:

message A {
  string name = 1;
  string description = 2;
}

Updating the server side first and not updating the client side (react based) leads to the following error:

ConnectError: [invalid_argument] cannot decode message api.v1.A from JSON: key "description" is unknown
    at LN (connect-error.js:102:16)
    at parse (serialization.js:114:23)

Which breaks the client.

Is there any way to make the client side behave like the go deserializer to simply ignore unknown properties ?

Environment (please complete the following information):

• @bufbuild/connect version: (for example, 0.8.6)
• @bufbuild/connect-web version: (for example, 0.8.6)
• @bufbuild/connect-go version: (for example, 1.7.0) (on the server side)
• Frontend framework and version: (for example, [email protected])

[timostamm]

Hey @majst01, you can set JSON options on the Transport:

https://github.com/bufbuild/connect-es/blob/29dc336bff2246044a9ac331ee70fedcfdcfa46c/packages/connect-web/src/connect-transport.ts#L96-L99

You'll want to set it as { ignoreUnknownFields: true }, following the definition here.

We'll add this to the documentation on connect.build, thanks for opening the issue!

[majst01]

This was fast, thanks a lot @timostamm

[timostamm]

For posterity: We changed the default behavior in #642 to ignore unknown fields by default. The change was released in v0.10.0.