Files
openfoodnetwork/app/models
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-09-12 23:19:05 +09:00
2024-01-29 13:21:13 +11:00
2023-09-12 23:19:05 +09:00
2023-09-12 23:19:05 +09:00
2023-12-11 08:26:32 +01:00
2023-09-12 23:19:05 +09:00
2023-06-23 09:08:04 +09:00
2024-01-17 15:16:51 +11:00