flores 0.0.1 → 0.0.2
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/.rubocop.yml +70 -0
- data/LICENSE.txt +662 -0
- data/Makefile +0 -19
- data/examples/analyze_number.rb +17 -0
- data/examples/socket_acceptance_spec.rb +25 -24
- data/examples/socket_analyze_spec.rb +18 -1
- data/examples/socket_stress_spec.rb +20 -3
- data/flores.gemspec +2 -3
- data/lib/randomized.rb +47 -17
- data/lib/rspec/stress_it.rb +82 -38
- data/spec/randomized_spec.rb +61 -24
- metadata +4 -2
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA1:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 93d262135443a719e7d26ac03f57cc016d63a216
|
|
4
|
+
data.tar.gz: d92cf5cb04a2553c1369948f2cd13d452bee6bff
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 72e01594ea803e4fc901cb5e9e825524045cc9812cf9b7f2d1430363f8733907b1a5949677e902159198056af873c2ec677f392c41dd56f9cef01c3a4126ad0a
|
|
7
|
+
data.tar.gz: 0e9b10da498eee2d17b2f3e7557f61e151c1adb2fa08a14ed7e4094cd7a38c4b15b83ee8516cb59d1734b2a145c0c52edad65d93ca0e34f407dc94ce2c71c8ed
|
data/.rubocop.yml
ADDED
|
@@ -0,0 +1,70 @@
|
|
|
1
|
+
# Let's not argue over this...
|
|
2
|
+
StringLiterals:
|
|
3
|
+
Enabled: false
|
|
4
|
+
|
|
5
|
+
# I can't find a reason for raise vs fail.
|
|
6
|
+
SignalException:
|
|
7
|
+
Enabled: false
|
|
8
|
+
|
|
9
|
+
# I can't find a reason to prefer 'map' when 'collect' is what I mean.
|
|
10
|
+
# I'm collecting things from a list. Maybe someone can help me understand the
|
|
11
|
+
# semantics here.
|
|
12
|
+
CollectionMethods:
|
|
13
|
+
Enabled: false
|
|
14
|
+
|
|
15
|
+
# Why do you even *SEE* trailing whitespace? Because your editor was
|
|
16
|
+
# misconfigured to highlight trailing whitespace, right? Maybe turn that off?
|
|
17
|
+
# ;)
|
|
18
|
+
TrailingWhitespace:
|
|
19
|
+
Enabled: false
|
|
20
|
+
|
|
21
|
+
# Line length is another weird problem that somehow in the past 40 years of
|
|
22
|
+
# computing we don't seem to have solved. It's a display problem :(
|
|
23
|
+
LineLength:
|
|
24
|
+
Max: 9000
|
|
25
|
+
|
|
26
|
+
# %w() vs [ "x", "y", ... ]
|
|
27
|
+
# The complaint is on lib/pleaserun/detector.rb's map of OS=>Runner,
|
|
28
|
+
# i'll ignore it.
|
|
29
|
+
WordArray:
|
|
30
|
+
MinSize: 5
|
|
31
|
+
|
|
32
|
+
# A 20-line method isn't too bad.
|
|
33
|
+
MethodLength:
|
|
34
|
+
Max: 20
|
|
35
|
+
|
|
36
|
+
# Hash rockets (=>) forever. Why? Not all of my hash keys are static symbols.
|
|
37
|
+
HashSyntax:
|
|
38
|
+
EnforcedStyle: hash_rockets
|
|
39
|
+
|
|
40
|
+
# I prefer explicit return. It makes it clear in the code that the
|
|
41
|
+
# code author intended to return a value from a method.
|
|
42
|
+
RedundantReturn:
|
|
43
|
+
Enabled: false
|
|
44
|
+
|
|
45
|
+
# My view on a readable case statement seems to disagree with
|
|
46
|
+
# what rubocop wants and it doesn't let me configure it other than
|
|
47
|
+
# enable/disable.
|
|
48
|
+
CaseIndentation:
|
|
49
|
+
Enabled: false
|
|
50
|
+
|
|
51
|
+
# module This::Module::Definition is good.
|
|
52
|
+
Style/ClassAndModuleChildren:
|
|
53
|
+
Enabled: true
|
|
54
|
+
EnforcedStyle: compact
|
|
55
|
+
|
|
56
|
+
# "in interpolation #{use.some("double quotes is ok")}"
|
|
57
|
+
Style/StringLiteralsInInterpolation:
|
|
58
|
+
Enabled: true
|
|
59
|
+
EnforcedStyle: double_quotes
|
|
60
|
+
|
|
61
|
+
# Long-block `if !something ... end` are more readable to me than `unless something ... end`
|
|
62
|
+
Style/NegatedIf:
|
|
63
|
+
Enabled: false
|
|
64
|
+
|
|
65
|
+
Style/NumericLiterals:
|
|
66
|
+
MinDigits: 6
|
|
67
|
+
|
|
68
|
+
# This kind of style "useless use of %x" assumes code is write-once.
|
|
69
|
+
Style/UnneededPercentX:
|
|
70
|
+
Enabled: false
|