Remove placeholders (#2)

* Mark repeated fields

* Regenerate files

* Remove placeholders

* Fix groups in post_init

* Fix test

* Fix bugs

* Fix test

* Right type for default values of enum fields

* Fix default value for field in group

* Add repeated in message definition in tests

* Fix missing messages in to_dict and to_pydict

* Fix pickling tests

* Fix placeholders in tests

* Remove serialize_on_wire from condition

* Remove serialize_on_wire

* Remove serialize_on_wire tests

* Remove wrong test

* Load test directly

* Fix match test

* Fix README

* Add error (tofix)

* Fix to_dict / to_pydict test

* Don't include default value in __repr__

* Fix snake_case test

* Remove useless try / catch

* Manually add missing repeated parameters in compiled file

* Fix compilation errors

* Fix enum compilation

* Compile fields in oneof as optional

* Fix from_pydict

* Remove Rust codec

* Mark messages as optional

* Format the code

* Move match test to other file

* Remoev useless prints

* Remove serialized_on_wire from documentation

* Simplify lambda functions

* Format the code

---------

Co-authored-by: Adrien Vannson <adrien.vannson@gardacp.com>

Author: AdrienVannson

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:
@@ -283,11 +269,11 @@ On Python 3.10 and later, you can use a `match` statement to access the provided
 ```py
 test = Test()
 match test:
-    case Test(on=value):
+    case Test(on=bool(value)):
         print(value)  # value: bool
-    case Test(count=value):
+    case Test(count=int(value)):
         print(value)  # value: int
-    case Test(name=value):
+    case Test(name=str(value)):
         print(value)  # value: str
     case _:
         print("No value provided")

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
 ~~~~~~~~~~~~~~