hash_mapper 0.1.2 → 0.1.3
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +1 -1
- data/Rakefile +5 -0
- data/lib/hash_mapper/version.rb +1 -1
- data/spec/spec_helper.rb +5 -2
- metadata +1 -1
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 3fcd7f8475d938cf6002450682f5e4bf17865074
|
4
|
+
data.tar.gz: a16e082eb53d60cf26fc99c67cbecb31c04787b0
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 1075ad77863f0b6ec01b6178a1257d5bb676c556dfe02183dfa5bb3ec67e90548871e58943b3bb6e6e5fedf87a77172793e089bb8c80ee9adbcc12f09007358e
|
7
|
+
data.tar.gz: ce2cdf149dd160c82ad29e441fa17f4eacde912b36fe31ac93f3e3edd74b74776747d94a83b5bdecef5ce5aef380c53e4a001f31e1117147d3e55723843ae4af
|
data/README.md
CHANGED
@@ -111,7 +111,7 @@ You can pass :to_i, :to_s or anything available method that makes sense. Don't f
|
|
111
111
|
You guessed it. That means that you can actually pass custom blocks to each to() definition as well. The following is similar to the previous example:
|
112
112
|
|
113
113
|
```ruby
|
114
|
-
map from('/one), to('/one'){|value| value.to_i}
|
114
|
+
map from('/one'), to('/one'){|value| value.to_i}
|
115
115
|
```
|
116
116
|
|
117
117
|
#### Custom value filtering
|
data/Rakefile
CHANGED
data/lib/hash_mapper/version.rb
CHANGED
data/spec/spec_helper.rb
CHANGED
@@ -5,9 +5,12 @@
|
|
5
5
|
#
|
6
6
|
# See http://rubydoc.info/gems/rspec-core/RSpec/Core/Configuration
|
7
7
|
RSpec.configure do |config|
|
8
|
-
config.treat_symbols_as_metadata_keys_with_true_values = true
|
9
8
|
config.run_all_when_everything_filtered = true
|
10
|
-
config.filter_run :
|
9
|
+
config.filter_run focus: true
|
10
|
+
|
11
|
+
config.expect_with :rspec do |c|
|
12
|
+
c.syntax = :should
|
13
|
+
end
|
11
14
|
end
|
12
15
|
|
13
16
|
$:.unshift(File.dirname(__FILE__) + '/../lib')
|