ditkrg/validates_timeliness
4
0
Fork 0
mirror of https://github.com/ditkrg/validates_timeliness.git synced 2026-01-22 22:06:45 +00:00
Code Issues Packages Projects Releases Wiki Activity

README tweaks and clarity

Browse Source
This commit is contained in:
Adam Meehan 2008-07-28 07:12:41 +10:00
parent 2ddc54b78d
commit 9fa3e3fa1d
1 changed files with 12 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
README
View File

@ -5,13 +5,10 @@
== DESCRIPTION: == DESCRIPTION:
Validate dates, times and datetimes for Rails 2.x. Plays nicely with new Validate dates, times and datetimes for Rails 2.x. Plays nicely with new Rails 2.1
features such as automatic timezone handling and dirty attributes. Allows features such as automatic timezone handling and dirty attributes. Allows you
date/time atttributes to behave like other attribute types by allowing you to add custom formats or remove defaults easily. This you can control what you
review the raw entered value before it is converted. think should be a valid date or time string.
Allows you add custom formats or remove defaults easily. This you can control
what you think should be a valid date or time string.
== FEATURES: == FEATURES:
@ -22,8 +19,8 @@ what you think should be a valid date or time string.
* Create new formats using very simple date/time format tokens * Create new formats using very simple date/time format tokens
* Adds better transparency of date/time attributes restoring ability to view * Restores ability to see raw value entered for date/time attributes with
raw value before type casting, which was lost in Rails 2.1. _before_type_cast modifier, which was lost in Rails 2.1.
* Respects new timezone features of Rails 2.1. * Respects new timezone features of Rails 2.1.
@ -205,12 +202,6 @@ remove a format stick this in an initializer file or environment.rb
Done! That format is no longer considered valid. Easy! Done! That format is no longer considered valid. Easy!
You can embed regular expressions in the format but no gurantees that it will
remain intact. If you avoid the use of any token characters and regexp dots or
backslashes as special characters in the regexp, it may well work as expected.
For special characters use POSIX character clsses for safety. See the ISO 8601
datetime for en example of of an embedded regular expression.
Ok, now I hear you say "Well I have format that I want to use but you don't have it". Ok, now I hear you say "Well I have format that I want to use but you don't have it".
Ahh, then add it yourself. Again stick this in an initializer file or environment.rb. Ahh, then add it yourself. Again stick this in an initializer file or environment.rb.
@ -218,6 +209,12 @@ Ahh, then add it yourself. Again stick this in an initializer file or environmen
Now "10 o'clock" will be a valid value. So easy, no more whingeing! Now "10 o'clock" will be a valid value. So easy, no more whingeing!
You can embed regular expressions in the format but no gurantees that it will
remain intact. If you avoid the use of any token characters and regexp dots or
backslashes as special characters in the regexp, it may well work as expected.
For special characters use POSIX character classes for safety. See the ISO 8601
datetime for an example of of an embedded regular expression.
Because formats are evaluated in order, adding a format which may be ambiguous Because formats are evaluated in order, adding a format which may be ambiguous
with an existing format, will mean your format is ignored. If you need to make with an existing format, will mean your format is ignored. If you need to make
your new format higher precedence than an existing format, you can include the your new format higher precedence than an existing format, you can include the