validation_contract 0.1.6 → 0.1.7
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +28 -0
- data/lib/validation_contract/version.rb +1 -1
- data/validation_contract.gemspec +2 -1
- metadata +4 -4
- data/validation_contract-0.1.5.gem +0 -0
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA1:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: a71c88ac926337c42b08a5b767321b6b3c49346e
|
|
4
|
+
data.tar.gz: 4698ef0f6118e325672c0e0816f17a0b282022e6
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 63486f2592b3509fa1e91ea96c0d008ad6f3b5e9f68b3156c3093bb9d84d54ac37c9d621acd5798204cfa5c9bd5cb0fb0071583a4e26f6be22d9fa7ac6a3e673
|
|
7
|
+
data.tar.gz: aea838a1e4adeb6dc144acc213f94173782256e43ac1cebb1ca9302ca78891eb8f25a63a7cd770da6c55d2dcacdefdb700916005669206c444fd92c5801cfc14
|
data/README.md
CHANGED
|
@@ -41,3 +41,31 @@ Suggestion for the validations. Perform all the necessary validations and then b
|
|
|
41
41
|
end
|
|
42
42
|
|
|
43
43
|
This will check if there is any invalid field, if there is an arry returned with all the validations. This type of validation is very good for APIs that are being used for a form with many fields, so you return to the FRONT all errors at one time.
|
|
44
|
+
|
|
45
|
+
## Validations
|
|
46
|
+
|
|
47
|
+
- is_required => 'validate if field is required'
|
|
48
|
+
- has_min_len => 'check if the field has a minimum of characters'
|
|
49
|
+
- has_max_len => 'checks if the field has a maximum of characters'
|
|
50
|
+
- is_fixed_len => Checks if there is an x quantity of '
|
|
51
|
+
- is_email => 'Check if email is valid'
|
|
52
|
+
- errors => 'Return errors'
|
|
53
|
+
- clear => 'Clears the arry error'
|
|
54
|
+
- is_valid => 'Check whether this arry is valid or not'
|
|
55
|
+
|
|
56
|
+
|
|
57
|
+
## Contributing
|
|
58
|
+
|
|
59
|
+
1. Fork it
|
|
60
|
+
2. Create your feature branch (git checkout -b my-new-feature)
|
|
61
|
+
3. Commit your changes (git commit -am 'Added some feature')
|
|
62
|
+
4. Push to the branch (git push origin my-new-feature)
|
|
63
|
+
5. Create new Pull Request
|
|
64
|
+
|
|
65
|
+
## Contributors
|
|
66
|
+
|
|
67
|
+
[Ricardo Grassi](https://github.com/grassiricardo).
|
|
68
|
+
|
|
69
|
+
## License
|
|
70
|
+
|
|
71
|
+
ValidationContract is released under the [MIT License](http://www.opensource.org/licenses/MIT).
|
data/validation_contract.gemspec
CHANGED
|
@@ -11,7 +11,8 @@ Gem::Specification.new do |spec|
|
|
|
11
11
|
|
|
12
12
|
spec.summary = %q{Validations of the day day for your rails project.}
|
|
13
13
|
spec.description = %q{With this gem you will have several validations that are common on day day and that will make life much easier for dev. Validations can be returned in a simple and standardized way..}
|
|
14
|
-
spec.homepage =
|
|
14
|
+
spec.homepage = %q{https://github.com/grassiricardo/validation_contract}
|
|
15
|
+
spec.licenses = ["MIT"]
|
|
15
16
|
|
|
16
17
|
spec.files = `git ls-files -z`.split("\x0").reject do |f|
|
|
17
18
|
f.match(%r{^(test|spec|features)/})
|
metadata
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: validation_contract
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.1.
|
|
4
|
+
version: 0.1.7
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- grassiricardo
|
|
@@ -55,10 +55,10 @@ files:
|
|
|
55
55
|
- bin/setup
|
|
56
56
|
- lib/validation_contract.rb
|
|
57
57
|
- lib/validation_contract/version.rb
|
|
58
|
-
- validation_contract-0.1.5.gem
|
|
59
58
|
- validation_contract.gemspec
|
|
60
|
-
homepage:
|
|
61
|
-
licenses:
|
|
59
|
+
homepage: https://github.com/grassiricardo/validation_contract
|
|
60
|
+
licenses:
|
|
61
|
+
- MIT
|
|
62
62
|
metadata: {}
|
|
63
63
|
post_install_message:
|
|
64
64
|
rdoc_options: []
|
|
Binary file
|