feat: Crons

[arnauorriols]

https://docs--crons.deno.deno.net/deploy/reference/crons/

[arnauorriols]

• Be more explicit about crons being scheduled to each timeline right after explaining how to declare them.

[philhawksworth]

Cron or crons?

[arnauorriols]

Cron jobs?

[philhawksworth]

Is there a reason for us calling this feature Crons instead of Cron?

Cron feels more correct, with the descriptive plural form being "cron tasks" or "cron jobs" as we've used in the past and seems to be the wider norm

[arnauorriols]

I haven't really given it any thought. Now that you mention it though, my preference would be Cron Jobs.

[arnauorriols]

However, if we go with "Cron Jobs", we should update the UI accordingly. @donjo

[philhawksworth]

I think the feature should be Cron and that the UI should correspond. In prose and where we are talking about multiple registered cron items, "cron jobs" seems standard and appropriately descriptive

[donjo]

That sounds right to me, we can update the UI accordingly to match what is being proposed here.

[arnauorriols]

Renamed feature to "Cron", and normalized all references in text to "cron job(s)". See e71d5bc

[philhawksworth]

This traffic light status description appears before any mention of a UI in the console. Should the existence of the cron dashboard be mentioned first so that this is more meaningful?

[arnauorriols]

I could just remove the color column? it does not add much value.

[philhawksworth]

What happens if an attempt to use the same name is made on a single timeline?

[arnauorriols]

I'm not sure I understand what you mean

[philhawksworth]

There is a description here of what happens if the same name for a cron job is used in different timelines. I curious to know what happens if the sane name is used twice, perhaps in error, in a single timeline.

Deno.cron("cleanup-old-data", "0 * * * *", () => {
  console.log("Cleaning up old data...");
});

//....

Deno.cron("cleanup-old-data", "6 * * * *", () => {
  console.log("Cleaning up other old data...");
});

[arnauorriols]

Oh. That's a runtime error, and your revision will fail to warmup.

[philhawksworth]

• No concurrent executions of the same cron

What exactly does that mean? Could we be a tiny bit more descriptive here in the interest of driving out any ambiguity?

[arnauorriols]

Honestly, besides the billing point, the rest are already explained in length above. I'm considering removing the section alltogether, and adding a billing section explaining how billing works

[philhawksworth]

Looking good!

I've added some questions and comments.

A fundamental one is about the naming of this as Crons vs Cron, which might bring about the need for a few edits for consistency depending on what is decided.

[philhawksworth]

LGMT