Callback should be called when `duration` is `Duration.zero` about pausable_timer

[Aturex1]

It didn't work because of a logical error. I tested the minimum example above and it seemed to work properly. Closing this as a (logical) bug not of the package.
I'm sorry to have kept you in suspense with something so unnecessary.

[mateusfccp]

@Aturex1 How should it behave in this case? If the duration of the period is zero, the callback would in theory be called infinite times, which is obviously not what we want here.

[Aturex1]

The callback should be called once (if the timer is not periodic). However, if it is a periodic timer it shouldn't be called.

[mateusfccp]

The callback should be called once (if the timer is not periodic). However, if it is a periodic timer it shouldn't be called.

So the issue is specifically for non-periodic timer. The behavior described seems to make sense. I am only worried if this is the same behavior as the dart:core's Timer, as we want to be consistent with it.

[mateusfccp]

I just tried the dart:core's behavior and this is definitely a bug. Even with a periodic timer it should work.

Indeed, even our documentation suggests that this should work:

/// The [duration] must be equals or bigger than [Duration.zero].
/// If it is [Duration.zero], the [callback] will still not be called until
/// the timer is [start]ed.

I don't know if this worked before or not. This may have been introduced in the latest refactor.