Let's say, for example, we are allowing users to rate songs and artists. I would like to be able to get a single, ordered list of recommendations for a user that includes both songs and artists based on the likelihood that the user will like it, regardless of its class.

I would be willing to build the list myself by calling recommended_songs and recommended_artists and merging the lists if I

I ran into a situation where there was a stupid mistake in one of our cron and we didn't notice it.

I believe we do parse crons already in app to queue jobs in time. So why not complain if some crons contain errors, i.e are not parse-able. I believe they are silently ignore as of now.

If i can get some guidance i will be happy to contribute this. We may add a configuration to raise exception

Something like #disable_all! will be useful for development environment, so you don't need to modify each worker to add a guard.

Is your feature request related to a problem? Please describe.

We just came across this project—it looks awesome! Thanks so much. We're hoping to use something like until_and_while_executing to prevent duplicate jobs from running or getting enqueued too many times, but we're worried about jobs hanging when they get picked up.

Describe the solution you'd like

I think the behavior

We should just throw an argument error if no block is provided to on_event.

Small but important quality of life thing for teams of any post-market-fit size.