scheduled_value 1.1.2 → 1.1.3
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/CHANGELOG.md +5 -1
- data/README.md +1 -2
- data/lib/scheduled_value/timespan.rb +4 -1
- data/lib/scheduled_value/version.rb +1 -1
- data/scheduled_value.gemspec +1 -1
- metadata +4 -4
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 156d1749f66958660a03ad85d99369cd6c17f888
|
4
|
+
data.tar.gz: 9769846b2b3863e6ab520a330c569209d60e78fe
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 4771ff29c9b64c31b13e94d7a37c2fce246b49f146deffb3a43470e35687f70452f433ce1b92ab0b47c7088dfb627918a9050d83f0b2bcf6c53ee7471408bd21
|
7
|
+
data.tar.gz: 3a84b96224b79f806982303bb7010fbcc62eaa1c29cf382452f45db38295f4c4b0958eaaa1605bdfeeb32fa8e399fa114f152541ad4d371d8e3578a170b5e3b9
|
data/CHANGELOG.md
CHANGED
@@ -1,3 +1,7 @@
|
|
1
|
+
# 1.1.3 - September 27, 2017
|
2
|
+
|
3
|
+
* Don't assume 'date' and 'time' are already required by the time we require 'scheduled_value/timespan'
|
4
|
+
|
1
5
|
# 1.1.2 - May 22, 2017
|
2
6
|
|
3
7
|
* Bug fix: use setters in initializers so that custom conversions will work when deserializing ScheduledValues
|
@@ -12,4 +16,4 @@
|
|
12
16
|
|
13
17
|
# 1.0.0 - December 24, 2016
|
14
18
|
|
15
|
-
* Initial public release.
|
19
|
+
* Initial public release.
|
data/README.md
CHANGED
@@ -1,6 +1,6 @@
|
|
1
1
|
# ScheduledValue
|
2
2
|
|
3
|
-
[![Gem Version](https://badge.fury.io/rb/scheduled_value.svg)](https://badge.fury.io/rb/scheduled_value) ![
|
3
|
+
[![Gem Version](https://badge.fury.io/rb/scheduled_value.svg)](https://badge.fury.io/rb/scheduled_value) [![Build Status](https://travis-ci.org/neinteractiveliterature/scheduled_value.svg?branch=master)](https://travis-ci.org/neinteractiveliterature/scheduled_value)
|
4
4
|
|
5
5
|
ScheduledValue provides a set of Ruby classes for representing values that change over time based on a schedule. One way to think about this is that for a regular variable, you could reasonably ask "what is its value?" For a ScheduledValue, you have to ask "what is its value *right now*?" Some examples of this might be:
|
6
6
|
|
@@ -36,4 +36,3 @@ To install this gem onto your local machine, run `bundle exec rake install`. To
|
|
36
36
|
## Contributing
|
37
37
|
|
38
38
|
Bug reports and pull requests are welcome on GitHub at https://github.com/neinteractiveliterature/scheduled_value.
|
39
|
-
|
data/scheduled_value.gemspec
CHANGED
@@ -20,6 +20,6 @@ Gem::Specification.new do |spec|
|
|
20
20
|
spec.require_paths = ["lib"]
|
21
21
|
|
22
22
|
spec.add_development_dependency "bundler", "~> 1.10"
|
23
|
-
spec.add_development_dependency "rake", "~>
|
23
|
+
spec.add_development_dependency "rake", "~> 12.1"
|
24
24
|
spec.add_development_dependency "minitest"
|
25
25
|
end
|
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: scheduled_value
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 1.1.
|
4
|
+
version: 1.1.3
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Nat Budin
|
8
8
|
autorequire:
|
9
9
|
bindir: exe
|
10
10
|
cert_chain: []
|
11
|
-
date: 2017-
|
11
|
+
date: 2017-09-27 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: bundler
|
@@ -30,14 +30,14 @@ dependencies:
|
|
30
30
|
requirements:
|
31
31
|
- - "~>"
|
32
32
|
- !ruby/object:Gem::Version
|
33
|
-
version: '
|
33
|
+
version: '12.1'
|
34
34
|
type: :development
|
35
35
|
prerelease: false
|
36
36
|
version_requirements: !ruby/object:Gem::Requirement
|
37
37
|
requirements:
|
38
38
|
- - "~>"
|
39
39
|
- !ruby/object:Gem::Version
|
40
|
-
version: '
|
40
|
+
version: '12.1'
|
41
41
|
- !ruby/object:Gem::Dependency
|
42
42
|
name: minitest
|
43
43
|
requirement: !ruby/object:Gem::Requirement
|