Great that you're creative with your workaround :)!
Another way could be a model validation that adds an error to the instance instead of parsing an invalid date to a unintended one. For example, you could use a custom validation like this:
# in user.rb modelvalidate:ensure_birthdate_format,if: ->{birthdate.present?}# ...privatedefensure_birthdate_formatbirthdate_before_type_cast.to_daterescueArgumentErrorerrors.add(:birthdate,:invalid)end
Oh you put me to shame Michael! You're right, I could definitely move this to the model and write a custom validation. Quick question though, won't _before_type_cast return a hash? I'm not sure if I'd be able to call #to_date on it. But I suppose I could just pass the values into a Date object again and rescue the error. Either way, it's a great idea to keep this logic out of the controller! Thank you!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Great that you're creative with your workaround :)!
Another way could be a model validation that adds an error to the instance instead of parsing an invalid date to a unintended one. For example, you could use a custom validation like this:
Oh you put me to shame Michael! You're right, I could definitely move this to the model and write a custom validation. Quick question though, won't
_before_type_castreturn a hash? I'm not sure if I'd be able to call#to_dateon it. But I suppose I could just pass the values into aDateobject again and rescue the error. Either way, it's a great idea to keep this logic out of the controller! Thank you!