Error Reporting - Date out of range

[caseywatts]

When I try to update dates on a reservation and I choose illegal dates (like February 30th) it gives the

"We're sorry, but something went wrong.
We've been notified about this issue and we'll take a look at it shortly."

error, instead of something more helpful. Any chance we can fix that?

If it could say something like "Invalid date range" instead of just the generic error message, THAT would be immensely helpful.

[tchaicowsky]

Update: Now instead of giving a "We're sorry, something went wrong" message, the app just breaks:

ArgumentError in ApplicationController#update_cart
invalid date

[caseywatts]

The "we're sorry, something went wrong" happens on the production server, life, as a prettier frontent. The ArgumentError... is ugly but informational for our development server. Same problem!
I think validations would do the trick~!

[ebmaher]

with the new version of date searches (calendar! yay!) this shouldn't ever be a problem. closing issue.

[caseywatts]

Even if we try to break it? :O

[ebmaher]

womp. this can be broken. working on it

[dgoerger]

datepicker successfully prevents the input of invalid dates. tested with 06/31/2012 and 02/29/2013. resolving.

[adambray]

You can still enter invalid dates by hand, and the update_cart method will throw an ArguementError: invalid date silently.

We should have error messages displayed in this case.