Files
openfoodnetwork/spec
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-11-30 13:47:39 +11:00
2023-09-16 09:05:31 +09:00
2024-02-14 11:16:59 +11:00
2024-02-07 15:27:51 +11:00
2023-09-21 22:58:42 +09:00
2024-02-15 14:57:13 +11:00
2024-01-25 14:14:58 +11:00
2023-09-25 13:15:38 +09:00
2024-02-15 14:57:13 +11:00
2023-08-08 11:36:31 +01:00
2023-12-22 13:20:14 +01:00