[BUG] can't update an existing compliance entry

[cnonob]

When trying to edit an existing compliance entry (insurance for example) with new values, change date to recurring etc, I get a "please fix the errors in the form before submitting"
That error happens even if we don't change anything

[cnonob]

Same issue if we try to create a new maintenance or compliance entry

[pdlourenco]

This looks like it may have been fixed by #237 (merged 22 Aug, after this
report), though it'd be good to have confirmation from someone who hit it.

The symptom you describe — the error appearing even with no changes made —
matches a date-parsing bug in the compliance schema. The end-date validation
used to be:

new Date(data.endDate) > new Date(data.startDate)

but those values are in the user's configured display format. For a
day-first format, new Date('13/08/2027') returns Invalid Date, so the
comparison is always false and the form fails validation on open, before you
touch anything. Anyone on dd/MM/yyyy (most of Europe) would see it on every
existing entry with an end date; anyone on MM/dd/yyyy mostly wouldn't.

#237 replaced that with a complianceFormSchema(dateFormat) that parses using
the configured format.

I checked on current dev: an unchanged insurance entry with dd/MM/yyyy
dates and a fixed end date now validates, as does converting the same entry to
yearly recurrence. Both were the scenarios described here.

@cnonob — if you can re-test on the latest dev image, that would confirm it.

One caveat: I verified the date-format cause specifically. If the error still
appears after updating, it's a different path and the details would be worth
adding here (which compliance type, the date format in Settings, and whether
the entry has an end date).