Crash when field has the same name as a system type #53
Labels
bug
Something isn't working
has test
Has a (xfail) test that verifies the bugfix or feature
medium priority
small
Low effort issue that can easily be picked up
Projects
Milestone
This
oneof
definition generates valid Python code, but later it is not possible to parse or create an instance ofTileValue
because the name of the field is the same as the type. Should betterproto rename such fields automatically, or at least throw an error during the code generation? I spent considerable time trying to understand why this line was sayingt
is not a class:python-betterproto/betterproto/__init__.py
Line 594 in 3546f55
The text was updated successfully, but these errors were encountered: