Files
openfoodnetwork/spec/system/admin
David Cook 7164cbd0bd Don't validate numericality if blank
This avoids unnecessary second message when left blank:
> can't be blank
> is not a number

Ok this is a little confusing. Why is there a  separate presence check above, and why is it only for measurable units, when we still require a number for _all_ units? Because, for 'items', we allow a blank value then auto-set it to 1.
I don't know if it's really necessary, but that's how it currently works...
2024-02-16 08:51:53 +11:00
..
2023-12-22 13:20:14 +01:00
2023-12-08 13:33:36 +01:00
2023-09-29 08:51:48 +09:00
2023-05-21 00:15:32 +01:00
2023-09-29 08:51:48 +09:00
2023-09-29 08:51:48 +09:00
2023-08-14 21:02:48 +01:00
2023-10-24 08:49:34 +09:00
2023-10-24 08:49:34 +09:00