Mattew S.

I would love to build. I'll see if I can take some time and help you with that. 🙂

> You say this is essential, but you provide no reasoning of _why_ it would be essential. I left out this possibility precisely because I figured it _wouldn't_ be essential....

> @HK-Mattew have you considered having your scheduled jobs explicitly save their results to a persistent data store at the end of their execution? Hello Yes, I use it like...

> I guess this could be supported as an opt-in feature, by adding a `result_expiration_time` parameter to schedules which defaults to 0. Hi @agronholm Exactly, this should be an optional...

Only one person left to review. Anyone?

Hello, See my code example: ```python from wtforms import Form, SelectField, validators class MyForm(Form): def render_visitor_timer_choices(): choices = [ (1, 'One'), (2, 'Two'), (3, 'Three'), (4, 'Four') ] return choices...

**Hello,** I use data= instead of formdata= because I'm using wtforms to validate data received through my api created with Flask-Restfull. Then I receive the request data through: ```python data...

Hi @Daverball , I'm generating the raunchy JSON payload from javascript. In this case I create the object. I already use Pydantic models, but I didn't think about putting them...

@Daverball I can't send the raw data. Because I use the API to submit form data from my website and also to use the API externally (outside the browser).

> 1. The `stop()` method is a bit too forceful (by default), and should probably not cancel the scheduler's task group However, the expected behavior when the job is completed...