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
Assuming we don't completely overhaul the way beat messages are handled; there are several classes that transform the argument for proper logging. The arguments are transformed in the constructor which in most cases is sufficient but should the tester ever want to manipulate the attribute after the object has been instantiated the logging will not match.
example:
classMakeNote:
defdescribe(self: SelfMakeNote) ->str:
returnf"Make a note under {represent_prop(self.key)}."@beat("{} jots something down under {key_to_log}.")defperform_as(self: SelfMakeNote, the_actor: Actor) ->None:
...
def__init__(
self: SelfMakeNote,
question: T_Q,
key: Optional[str] =None,
) ->None:
self.question=questionself.key=keyself.key_to_log=represent_prop(key)
These attributes should be turned into a more dynamic property.
The text was updated successfully, but these errors were encountered:
Assuming we don't completely overhaul the way
beat
messages are handled; there are several classes that transform the argument for proper logging. The arguments are transformed in the constructor which in most cases is sufficient but should the tester ever want to manipulate the attribute after the object has been instantiated the logging will not match.example:
These attributes should be turned into a more dynamic property.
The text was updated successfully, but these errors were encountered: