-
Notifications
You must be signed in to change notification settings - Fork 184
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove frozenMessageModificationHandler #175
Comments
osa1
added a commit
to osa1/protobuf.dart
that referenced
this issue
May 9, 2022
See google#175 for the problems with this API. Internally this API is not used. However this is still a breaking change and will be released with the next major release. Fixes google#175
osa1
added a commit
to osa1/protobuf.dart
that referenced
this issue
May 9, 2022
See google#175 for the problems with this API. Internally this API is not used. However this is still a breaking change and will be released with the next major release. Fixes google#175
osa1
added a commit
to osa1/protobuf.dart
that referenced
this issue
May 9, 2022
See google#175 for the problems with this API. Internally this API is not used. However this is still a breaking change and will be released with the next major release. Fixes google#175
osa1
added a commit
that referenced
this issue
Jun 15, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently we have
frozenMessageModificationHandler
that is used to throw when a frozen message is changed. It can be customized.FrozenPbList
and a frozenPbMap
do not use this, but will just throw.This is inconsistent. And it is not clear to me how much is gained by the hook.
I suggest we remove the handler from the public API, and always just throw.
The text was updated successfully, but these errors were encountered: