Remove serialized_on_wire from documentation

AdrienVannson · AdrienVannson · commit 64e6dc139b4a · 2024-11-13T17:58:46.000+01:00
diff --git a/README.md b/README.md
@@ -248,20 +248,6 @@ For compatibility the default is to convert field names to `camelCase`. You can
 MyMessage().to_dict(casing=betterproto.Casing.SNAKE)
 ```
 
-### Determining if a message was sent
-
-Sometimes it is useful to be able to determine whether a message has been sent on the wire. This is how the Google wrapper types work to let you know whether a value is unset, set as the default (zero value), or set as something else, for example.
-
-Use `betterproto.serialized_on_wire(message)` to determine if it was sent. This is a little bit different from the official Google generated Python code, and it lives outside the generated `Message` class to prevent name clashes. Note that it **only** supports Proto 3 and thus can **only** be used to check if `Message` fields are set. You cannot check if a scalar was sent on the wire.
-
-```py
-# Old way (official Google Protobuf package)
->>> mymessage.HasField('myfield')
-
-# New way (this project)
->>> betterproto.serialized_on_wire(mymessage.myfield)
-```
-
 ### One-of Support
 
 Protobuf supports grouping fields in a `oneof` clause. Only one of the fields in the group may be set at a given time. For example, given the proto:
diff --git a/docs/migrating.rst b/docs/migrating.rst
@@ -19,30 +19,6 @@ regenerating your protobufs of course) although there are some minor differences
     :meth:`betterproto.Message.__bytes__` respectively.
 
 
-Determining if a message was sent
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Sometimes it is useful to be able to determine whether a message has been sent on
-the wire. This is how the Google wrapper types work to let you know whether a value is
-unset (set as the default/zero value), or set as something else, for example.
-
-Use ``betterproto.serialized_on_wire(message)`` to determine if it was sent. This is
-a little bit different from the official Google generated Python code, and it lives
-outside the generated ``Message`` class to prevent name clashes. Note that it only
-supports Proto 3 and thus can only be used to check if ``Message`` fields are set.
-You cannot check if a scalar was sent on the wire.
-
-.. code-block:: python
-
-    # Old way (official Google Protobuf package)
-    >>> mymessage.HasField('myfield')
-    True
-
-    # New way (this project)
-    >>> betterproto.serialized_on_wire(mymessage.myfield)
-    True
-
-
 One-of Support
 ~~~~~~~~~~~~~~
 
