Skip to content

to_dict on empty nested types #200

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.

Sign up for GitHub

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

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
+9 −4
Open

to_dict on empty nested types #200

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
6ad9bab
to_dict on empty nested types (https://github.com/danielgtaylor/pytho…
kilimnik Jan 19, 2021
cef8f71
Removed lazy initialization
kilimnik Jan 20, 2021
9b7dd26
removed lazy initialization from tests
kilimnik Jan 20, 2021
d213abc
Fixed formatting
kilimnik Jan 20, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions tests/test_features.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ class Foo(betterproto.Message):
assert betterproto.serialized_on_wire(foo.bar) is False

# Serialized after setting something
foo.bar.baz = 1
foo.bar = Bar(baz=1)
Copy link
Collaborator

@Gobot1234 Gobot1234 Jan 20, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changing all this is a regression if this PR breaks this

Copy link
Author

@kilimnik kilimnik Jan 20, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know that isn't great. My PR would break lazy initialization. If you want to keep that, I have to think of another implementation. But lazy initialization also isn't in the google implementation, so I thought it wouldn't be important.

Copy link
Collaborator

@Gobot1234 Gobot1234 Jan 20, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well breaking things isn't good. I know how this can be fixed it's been discussed before but it involves every field having a serialized attribute or similar.

assert betterproto.serialized_on_wire(foo.bar) is True

# Still has it after setting the default value
Expand Down Expand Up @@ -130,7 +130,7 @@ class Foo(betterproto.Message):
assert foo.bar == 0
assert betterproto.which_one_of(foo, "group1")[0] == "baz"

foo.sub.val = 1
foo.sub = Sub(val=1)
assert betterproto.serialized_on_wire(foo.sub)

foo.abc = "test"
Expand Down Expand Up @@ -348,7 +348,7 @@ def test_recursive_message_defaults():
assert msg != RecursiveMessage(
name="bob", intermediate=Intermediate(42), child=RecursiveMessage(name="jude")
)
msg.child.child.name = "jude"
msg.child = RecursiveMessage(child=RecursiveMessage(name="jude"))
assert msg == RecursiveMessage(
name="bob",
intermediate=Intermediate(42),
Expand Down