validates_email_format_of 1.5.0 → 1.5.1
Sign up to get free protection for your applications and to get access to all the features.
- data/lib/validates_email_format_of.rb +4 -4
- metadata +3 -3
@@ -2,7 +2,7 @@
|
|
2
2
|
module ValidatesEmailFormatOf
|
3
3
|
require 'resolv'
|
4
4
|
|
5
|
-
VERSION = '1.5.
|
5
|
+
VERSION = '1.5.1'
|
6
6
|
|
7
7
|
MessageScope = defined?(ActiveModel) ? :activemodel : :activerecord
|
8
8
|
|
@@ -92,8 +92,8 @@ module ValidatesEmailFormatOf
|
|
92
92
|
next
|
93
93
|
end
|
94
94
|
|
95
|
-
next if local[i] =~ /[[:alnum:]]/
|
96
|
-
next if local[i] =~ LocalPartSpecialChars
|
95
|
+
next if local[i,1] =~ /[[:alnum:]]/
|
96
|
+
next if local[i,1] =~ LocalPartSpecialChars
|
97
97
|
|
98
98
|
# period must be followed by something
|
99
99
|
if ord == 46
|
@@ -120,7 +120,7 @@ module ValidatesEmailFormatOf
|
|
120
120
|
part.nil? or
|
121
121
|
part.empty? or
|
122
122
|
not part =~ /\A[[:alnum:]\-]+\Z/ or
|
123
|
-
part[0] == '-' or part[-1] == '-' # hyphen at beginning or end of part
|
123
|
+
part[0,1] == '-' or part[-1,1] == '-' # hyphen at beginning or end of part
|
124
124
|
}
|
125
125
|
|
126
126
|
# ipv4
|
metadata
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: validates_email_format_of
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 1.5.
|
4
|
+
version: 1.5.1
|
5
5
|
prerelease:
|
6
6
|
platform: ruby
|
7
7
|
authors:
|
@@ -9,7 +9,7 @@ authors:
|
|
9
9
|
autorequire:
|
10
10
|
bindir: bin
|
11
11
|
cert_chain: []
|
12
|
-
date: 2011-09-
|
12
|
+
date: 2011-09-15 00:00:00.000000000Z
|
13
13
|
dependencies: []
|
14
14
|
description: Validate e-mail addresses against RFC 2822 and RFC 3696.
|
15
15
|
email: code@dunae.ca
|
@@ -52,7 +52,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
|
|
52
52
|
version: '0'
|
53
53
|
requirements: []
|
54
54
|
rubyforge_project:
|
55
|
-
rubygems_version: 1.8.
|
55
|
+
rubygems_version: 1.8.10
|
56
56
|
signing_key:
|
57
57
|
specification_version: 3
|
58
58
|
summary: Validate e-mail addresses against RFC 2822 and RFC 3696.
|