We want to have the following behavior: 1. created_at is set by default, but can be overridden. 2. updated_at is not set on initial crea

This also serves as an example of a service class, which encapsulates a flow (start & finish) + one-off action (upload_local) into a namespac

This also serves as an example of a service class, which encapsulates 2 different behaviors (create & update) under a namespace. Meaning

This is an example from this blog post - https://www.hacksoft.io/blog/django-jsonfield-incrementation-with-f-expressions

This is an example from this blog post - https://www.hacksoft.io/blog/django-jsonfield-incrementation-with-f-expressions Django docs refe

This is an example model, to be used as reference in the Styleguide, when discussing model validation via constraints.

DRF SessionAuthentication is enforcing CSRF, which may be problematic. That's why we want to make sure we are exempting any kind of CSRF chec

We use a class, just for namespacing convenience.

We want to test the following: 1. A start-upload-finish cycle, where we patch the presign generation with local upload storage.

Example usage: future_roster1 = FutureRosterFactory() future_roster2 = FutureRosterFactory(start_after=future_roster1.end_date)

We use a class, just for namespacing convenience.