Expected Behavior
As specified in https://docs.dapr.io/developing-applications/building-blocks/actors/actors-timers-reminders/, period is an optional parameter. Therefore the python SDK methods should reflect that. However in both functions period is type hinted as a mandatory timedelta
async def register_reminder(
self,
name: str,
state: bytes,
due_time: timedelta,
period: timedelta,
ttl: Optional[timedelta] = None,
async def register_timer(
self,
name: Optional[str],
callback: TIMER_CALLBACK,
state: Any,
due_time: timedelta,
period: timedelta,
ttl: Optional[timedelta] = None,
I have confirmed that if you send None to period and just ignore the type error, everything functions fine according to the specified behaviour of the timer/reminder firing once.
Actual Behavior
In both functions period should be type hint as follows
period: Optional[timedelta]
or perhaps
period: Optional[timedelta] = None,
RELEASE NOTE: It's so minor I don't think it deserves one tbh, but it should still be fixed.
Expected Behavior
As specified in https://docs.dapr.io/developing-applications/building-blocks/actors/actors-timers-reminders/,
period is an optional parameter. Therefore the python SDK methods should reflect that. However in both functionsperiodis type hinted as a mandatorytimedeltaI have confirmed that if you send None to
periodand just ignore the type error, everything functions fine according to the specified behaviour of the timer/reminder firing once.Actual Behavior
In both functions period should be type hint as follows
period: Optional[timedelta]or perhaps
period: Optional[timedelta] = None,RELEASE NOTE: It's so minor I don't think it deserves one tbh, but it should still be fixed.