This is also a "side-effect" of sorts of when casting from a dataclass to a dict and back with "null" message-es getting set to "full" messages with "empty" or all-default values :-/
Not sure if it's better to fix that specifically or the one-of bug that it causes or both...?!?