Closed yingshaoxo closed 1 year ago
I found someone did a pull, but didn't get merged yet.
It's a protobuf issue, so it should be handled on protobuf repositiory. I asked protobuf.dart maintainer to take a look at the PR.
That being said: we can't just make these fields nullable because that is going to be massively breaking change. It probably could be an opt-in option for the protoc.
What I wrote
Here is my protobuf code:
Here is my grpc build command:
Here is my flutter code:
What I expect
The
email
property inCreateUserRequest
should be a null-safe variable, which means it could be nullThe
error
property inCreateUserResponse
should be a null-safe variable, which means it could be nullWhat I see is
They are all not null-able variables, it seems like the compiler ignores the
optional
string in the protobuf definition.