Fix: Better Handle arbitrary ISO 8601 strings after celery serializing

[shamoon]

Proposed change

See linked issue, #2019 did fix this but I think when parsing some iso 8601 strings it will fail e.g. if you pass 2022-01-15 to the API you get 2022-01-15T00:00:00Z which will fail with Invalid isoformat string: '2022-01-15T00:00:00Z'. So dont parse with datetime.fromisoformat use dateutil.parser.isoparse instead.

Fixes #2435

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Other (please explain)

Checklist:

• I have read & agree with the contributing guidelines.
• If applicable, I have tested my code for new features & regressions on both mobile & desktop devices, using the latest version of major browsers.
• If applicable, I have checked that all tests pass, see documentation.
• I have run all pre-commit hooks, see documentation.
• I have made corresponding changes to the documentation as needed.
• I have checked my modifications for any breaking changes.

[coveralls]

Pull Request Test Coverage Report for Build 3925763092

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.02%) to 92.717%

---

Totals
Change from base Build 3918958564:	-0.02%
Covered Lines:	5423
Relevant Lines:	5849

---

💛 - Coveralls

[stumpylog]

So the date coming in from the API isn't a valid ISO-8601 format, but merely something close to it?

Edit: I see the DRF DateTimeField could be configured to accept only an ISO format, maybe that's better to reject not formatting dates?

[shamoon]

Yea I thought about that, thats an option, I dont feel strongly but this see,ed an easy way to make the API a little more flexible. But again, defer to you.

[stumpylog]

A little flexibility seems alright.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion or issue for related concerns.