-
Notifications
You must be signed in to change notification settings - Fork 359
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Time.every improvement #884
Comments
Thanks for the issue! Make sure it satisfies this checklist. My human colleagues will appreciate it! Here is what to expect next, and if anyone wants to comment, keep these things in mind. |
It may make sense, but any design like this would need to be motivated by practical examples. If you have some of those, that can make a stronger suggestion. I'd recommend trying to refine the idea on Elm slack or the elm-discuss mailing list and opening a new issue if you feel you have compelling evidence. |
@kuznero, there are related questions for other "subscription generating functions". So it might be useful for you to have a look at: as well as at two existing mailing list threads (referenced over there): |
@jvoigtlaender thanks for the links |
Does it make sense to improve current
every : Time -> (Time -> msg) -> Sub msg
toevery : Time -> (Time -> Maybe msg) -> Sub msg
, such that event is fired not precisely everyN
something, but also does that based on some predicate that will be possible to implement inTime -> Maybe msg
lambda?The text was updated successfully, but these errors were encountered: