feat: allow forcing of event method for delayed resource

[sabbadino]

If I re-enqueue an object in the Updated event (returning a non null TimeSpan), "My" expectation is to receive the re-enqueued object in the original callback (Updated method) when the timespan expires.
Currently the object is re-pushed in the NotModified method

[buehler]

mhmm this is kind of the desired result (by now).
The idea behind it is, you can reschedule an object to be reconsidered after a time period. if it has not changed, then the notmodified event takes place. the idea behind it was to have a mechanism to check for db connections for example.

Maybe, the return type should be a tuple to give the possibility to set a specific method?
WDYT?

[sabbadino]

I agree with your proposal, still the default should be to call the original method IMHO. Enrico

…

On Sat, Oct 24, 2020, 09:43 Christoph Bühler ***@***.***> wrote: mhmm this is kind of the desired result (by now). The idea behind it is, you can reschedule an object to be reconsidered after a time period. if it has not changed, then the notmodified event takes place. the idea behind it was to have a mechanism to check for db connections for example. Maybe, the return type should be a tuple to give the possibility to set a specific method? WDYT? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#77 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACHKZFHDKX7Q3AAMD2Z5LPTSMKARPANCNFSM4S4LSS4Q> .

[buehler]

Hmm I need to think about a propper solution, since changing the default would be a breaking change.

[buehler]

This can be a new feature, to add the possibility to force a resource event method when using a delay.

[github-actions]

🎉 This issue has been resolved in version 4.3.0 🎉

The release is available on:

• GitHub release
• v4.3.0
• v4.3.0

Your semantic-release bot 📦🚀