You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Say I've compiled: class Priority(betterproto.Enum): PRIORITY_LOW = 0 PRIORITY_MEDIUM = 1 PRIORITY_HIGH = 2
Accessing the string value of each instance (which is defined by .toString()) is done similarly to Enum class in python, via Priority.PRIORITY_LOW.name, for example.
From usability point of view, I'd like to access this by the pythonic convention of str(Priority.PRIORITY_LOW). (i.e. add __str__ method to the compiled class).
Appreciate your consideration.
The text was updated successfully, but these errors were encountered:
Currently betterproto.Enum does already have a dunder str method which is just inherited from enum.Enum. With the 3.11(??) changes to the value of an enum's str I think this change makes sense an should be fine to include in 2.0.0 and my Enum branch along with a new repr method.
Say I've compiled:
class Priority(betterproto.Enum):
PRIORITY_LOW = 0
PRIORITY_MEDIUM = 1
PRIORITY_HIGH = 2
Accessing the string value of each instance (which is defined by
.toString()
) is done similarly toEnum
class in python, viaPriority.PRIORITY_LOW.name
, for example.From usability point of view, I'd like to access this by the pythonic convention of
str(Priority.PRIORITY_LOW)
. (i.e. add__str__
method to the compiled class).Appreciate your consideration.
The text was updated successfully, but these errors were encountered: