Closed jjkaye closed 13 years ago
iPhone is already passively enforcing this via the API. Matt will return an error if the conditions are not met - something to the effect of "You must pledge at least 1 Meal", etc.
I can tear up an old pillow for the feathers who's got the tar?
Great response, that's the kind of humor I'm looking for!
Oh you think I'm joking?? :P
That's the energy that's going to see this project through to the sick and twisted bitter end. :)
The API has always enforced at least one meal and one activity. We only took out the requirement that the number of meals must equal the number of activities.
Do we know if this is something the client experienced or something that they just wanted to make sure was a well understood requirement?
I think the lack of messaging is a cause for concern, we just need a way to implement that user feedback.
Having one issue for all devices is very vague and hard to track. Opening an issue for each of the apps.
I can verify that the API enforces the following max and min values:
ACTIVITY_MIN = 1,
ACTIVITY_MAX = 14,
MEAL_MIN = 1,
MEAL_MAX = 14,
and sends the following messages:
@adolfo32, @m14t, @jasco, @gabehayes this is minor but I know it's going to be annoying.
We need a check in place on the web/iPhone/Android apps during the sign up process on Step 2. We need to ensure that users pledge AT LEAST 1 meal and 1 activity. If they don't we need to prompt them with a message before they can move forward.
I realize in the past we had logic to handle unbalanced pledges, but this is is simply so they have pledges in the system when they register. I was certain at one point that Matt coded this logic into the API so I'm assuming it's still there.
Implementation guidelines:
You guys can tar and feather me AFTER we finish this project, deal? :)