Open crw opened 8 years ago
Let's think about the process flow:
This is where we split from current process. Today, with the paper form:
You are proposing:
I prefer your solution, but with the following caveats:
Make sense?
Thanks for a detailed analysis, I totally agree! It doesn't make sense to set a max until the meal is locked. And that max should automatically be the number of people signed up.
But why not just make it exactly like the current sheet? We could have meals lock automatically 48hrs before the meal, and at that point - but not before - the meal form would display an editable extras field that would be set to 0 by default.
Also, I've fixed the bug so users can now sign up if the max isn't set.
:+1:
I am good with your proposal.
With re: automated Close time, I am not convinced on that. Should we open another issue to discuss? Basically, 48 hours may not be a "one size fits all" type of thing, some may not go shopping until 8 hours before and are happy to leave it open until then. I don't really know. ¯(ツ)/¯ )
You're right; there's no point in having meals close automatically. I just remembered Ann saying she wanted to have her meals closed automatically. What if we added an auto-close checkbox to the meal form so it was an opt-in thing?
Yeah that works for me. It could even be opt-out, as I think most people would be happy with auto-close.
I was thinking this is what the max field would be for. Perhaps it'd be nice to generate an Extra Meals value dynamically with max - num. of attendees?