string_length_conformable 0.2.1 → 0.2.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. checksums.yaml +4 -4
  2. data/lib/string_length_conformable/version.rb +1 -1
  3. data/string_length_conformable.gemspec +9 -1
  4. metadata +15 -15
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 43e42b3c80a5a1b3bcbc2e9aa67516f657eee4d5eb0bd1a5e429b78ef3604d63
4
- data.tar.gz: 182aaa4a7586cb855e6ae431061827f2a77c52ddfbfa5b2e65ef86213851e094
3
+ metadata.gz: 11f6e238983fb8b5cf16c80a2276844cfcdbe68715125bc16ad24ae4df795513
4
+ data.tar.gz: 76c610eafdf7ba8afec2e312f09f030d68d2ff57b2a9c2613ce52a1b1569d276
5
5
  SHA512:
6
- metadata.gz: 7d0e73b0541248586789d1c6a54f1c4478375348e25e85e3bcd7f7365a417671dae0575823551eddd300e6699bdccca5ff5c34dd9d39112c87fc65a1034fe715
7
- data.tar.gz: 28a0a824dfae6b01cf3eb413407a6292c0bd5e5aa7c8974e03afe02590e1d5988e473aecb5c580df6ab1a479dd4c6f8ff4c441b51b02f1378bd20e97c52fc22c
6
+ metadata.gz: d53481114e511eeec0d389f969a9ffedb371908623e6cbdf6004eacbb4e495c36913a6dcc84966029392cda6dbe94fb08d029798e975c9a319014c57728ec66a
7
+ data.tar.gz: 7ec708e0332ccaba21f5e6dc0a74573ca680cec200daf1ce35499db00c46721f844549b2c27b76794ca5af062128339d0d6335825653eb3ff634858999b7a581
data/lib/string_length_conformable/version.rb CHANGED
@@ -1,3 +1,3 @@
1
1
  module StringLengthConformable
2
- VERSION = '0.2.1'.freeze
2
+ VERSION = '0.2.2'.freeze
3
3
  end
data/string_length_conformable.gemspec CHANGED
@@ -10,18 +10,26 @@ Gem::Specification.new do |spec|
10
10
 
11
11
  spec.summary = 'Gem for validate string length'
12
12
  spec.description = <<-TEXT
13
+ \n
13
14
  This gem resolves basically two problems.
15
+ \n
14
16
  ---
17
+ \n
15
18
  1. MySQL for strings(VARCHAR(255)) by default has limit 255 characters. And when developer left this attribute without any length validation, then it's possible to face with situation when user unintentionally or intentionally will pass in text field more characters. So, then, probably you will get 500...
19
+ \n
16
20
  ---
21
+ \n
17
22
  2. PostgreSQL. The maximum number of characters for variable unlimited length types (text, varchar) is undefined. There is a limit of size in bytes for all string types: In any case, the longest possible character string that can be stored is about 1 GB.
18
23
  And when developer left this attribute without any length validation, then it's possible to face with situation when user unintentionally or intentionally will try to full up your database with lots of GB of 'important' info.
24
+ \n
19
25
  ---
20
-
26
+ \n
21
27
  Both of this cases, I guess, are not very pleasant.
28
+ \n
22
29
 
23
30
  This gem adds default length validation for all string attributes.
24
31
  Except those which are already vlidated in standart rails way.
32
+ \n
25
33
 
26
34
  TEXT
27
35
 
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: string_length_conformable
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.2.1
4
+ version: 0.2.2
5
5
  platform: ruby
6
6
  authors:
7
7
  - Vladimir
@@ -52,20 +52,20 @@ dependencies:
52
52
  - - "~>"
53
53
  - !ruby/object:Gem::Version
54
54
  version: '3.0'
55
- description: |2+
56
- This gem resolves basically two problems.
57
- ---
58
- 1. MySQL for strings(VARCHAR(255)) by default has limit 255 characters. And when developer left this attribute without any length validation, then it's possible to face with situation when user unintentionally or intentionally will pass in text field more characters. So, then, probably you will get 500...
59
- ---
60
- 2. PostgreSQL. The maximum number of characters for variable unlimited length types (text, varchar) is undefined. There is a limit of size in bytes for all string types: In any case, the longest possible character string that can be stored is about 1 GB.
61
- And when developer left this attribute without any length validation, then it's possible to face with situation when user unintentionally or intentionally will try to full up your database with lots of GB of 'important' info.
62
- ---
63
-
64
- Both of this cases, I guess, are not very pleasant.
65
-
66
- This gem adds default length validation for all string attributes.
67
- Except those which are already vlidated in standart rails way.
68
-
55
+ description: " \n\n This gem resolves basically two problems.\n \n\n ---\n \n\n
56
+ \ 1. MySQL for strings(VARCHAR(255)) by default has limit 255 characters. And when
57
+ developer left this attribute without any length validation, then it's possible
58
+ to face with situation when user unintentionally or intentionally will pass in text
59
+ field more characters. So, then, probably you will get 500...\n \n\n ---\n \n\n
60
+ \ 2. PostgreSQL. The maximum number of characters for variable unlimited length
61
+ types (text, varchar) is undefined. There is a limit of size in bytes for all string
62
+ types: In any case, the longest possible character string that can be stored is
63
+ about 1 GB.\n And when developer left this attribute without any length validation,
64
+ then it's possible to face with situation when user unintentionally or intentionally
65
+ will try to full up your database with lots of GB of 'important' info.\n \n\n ---\n
66
+ \ \n\n Both of this cases, I guess, are not very pleasant.\n \n\n\n This gem
67
+ adds default length validation for all string attributes.\n Except those which
68
+ are already vlidated in standart rails way.\n \n\n\n"
69
69
  email:
70
70
  - raileanv@gmail.com
71
71
  executables: []