jiff-date_range 0.0.1alpha
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +7 -0
- data/.gitignore +8 -0
- data/.travis.yml +7 -0
- data/CODE_OF_CONDUCT.md +74 -0
- data/Gemfile +4 -0
- data/Gemfile.lock +24 -0
- data/LICENSE.txt +21 -0
- data/README.md +116 -0
- data/Rakefile +10 -0
- data/TODO +1 -0
- data/bin/console +14 -0
- data/bin/setup +8 -0
- data/jiff-date_range.gemspec +36 -0
- data/lib/jiff/date_range/version.rb +5 -0
- data/lib/jiff/date_range.rb +62 -0
- data/lib/jiff/month_mapper.rb +25 -0
- data/lib/jiff-date_range.rb +1 -0
- metadata +116 -0
checksums.yaml
ADDED
@@ -0,0 +1,7 @@
|
|
1
|
+
---
|
2
|
+
SHA256:
|
3
|
+
metadata.gz: 983cb28bf546134178793220406d8fb38b946e56216afe3f624e6ba43c14108f
|
4
|
+
data.tar.gz: 96eb20e723693e4a2edbbe7787a8c79f51b5d9e379e159b2bf41713069573ce1
|
5
|
+
SHA512:
|
6
|
+
metadata.gz: 55841617464abdae0f2a812f62978f35770ba0391698d3d99d36737a5aab7875b5a070fee2356e79aeb7ef13c0057a240fb05a32f65b76da11bc9259d278ae40
|
7
|
+
data.tar.gz: d10456e8f540f4fea44a8c53c40b90842d2cbaa96f6b34add990f797af811157e1f2ad81afa36c8ef705fa3d6d97e60942f7358e33c95f609a63a0f6c51bf3d0
|
data/.gitignore
ADDED
data/.travis.yml
ADDED
data/CODE_OF_CONDUCT.md
ADDED
@@ -0,0 +1,74 @@
|
|
1
|
+
# Contributor Covenant Code of Conduct
|
2
|
+
|
3
|
+
## Our Pledge
|
4
|
+
|
5
|
+
In the interest of fostering an open and welcoming environment, we as
|
6
|
+
contributors and maintainers pledge to making participation in our project and
|
7
|
+
our community a harassment-free experience for everyone, regardless of age, body
|
8
|
+
size, disability, ethnicity, gender identity and expression, level of experience,
|
9
|
+
nationality, personal appearance, race, religion, or sexual identity and
|
10
|
+
orientation.
|
11
|
+
|
12
|
+
## Our Standards
|
13
|
+
|
14
|
+
Examples of behavior that contributes to creating a positive environment
|
15
|
+
include:
|
16
|
+
|
17
|
+
* Using welcoming and inclusive language
|
18
|
+
* Being respectful of differing viewpoints and experiences
|
19
|
+
* Gracefully accepting constructive criticism
|
20
|
+
* Focusing on what is best for the community
|
21
|
+
* Showing empathy towards other community members
|
22
|
+
|
23
|
+
Examples of unacceptable behavior by participants include:
|
24
|
+
|
25
|
+
* The use of sexualized language or imagery and unwelcome sexual attention or
|
26
|
+
advances
|
27
|
+
* Trolling, insulting/derogatory comments, and personal or political attacks
|
28
|
+
* Public or private harassment
|
29
|
+
* Publishing others' private information, such as a physical or electronic
|
30
|
+
address, without explicit permission
|
31
|
+
* Other conduct which could reasonably be considered inappropriate in a
|
32
|
+
professional setting
|
33
|
+
|
34
|
+
## Our Responsibilities
|
35
|
+
|
36
|
+
Project maintainers are responsible for clarifying the standards of acceptable
|
37
|
+
behavior and are expected to take appropriate and fair corrective action in
|
38
|
+
response to any instances of unacceptable behavior.
|
39
|
+
|
40
|
+
Project maintainers have the right and responsibility to remove, edit, or
|
41
|
+
reject comments, commits, code, wiki edits, issues, and other contributions
|
42
|
+
that are not aligned to this Code of Conduct, or to ban temporarily or
|
43
|
+
permanently any contributor for other behaviors that they deem inappropriate,
|
44
|
+
threatening, offensive, or harmful.
|
45
|
+
|
46
|
+
## Scope
|
47
|
+
|
48
|
+
This Code of Conduct applies both within project spaces and in public spaces
|
49
|
+
when an individual is representing the project or its community. Examples of
|
50
|
+
representing a project or community include using an official project e-mail
|
51
|
+
address, posting via an official social media account, or acting as an appointed
|
52
|
+
representative at an online or offline event. Representation of a project may be
|
53
|
+
further defined and clarified by project maintainers.
|
54
|
+
|
55
|
+
## Enforcement
|
56
|
+
|
57
|
+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
|
58
|
+
reported by contacting the project team at rui.p.baltazar@gmail.com. All
|
59
|
+
complaints will be reviewed and investigated and will result in a response that
|
60
|
+
is deemed necessary and appropriate to the circumstances. The project team is
|
61
|
+
obligated to maintain confidentiality with regard to the reporter of an incident.
|
62
|
+
Further details of specific enforcement policies may be posted separately.
|
63
|
+
|
64
|
+
Project maintainers who do not follow or enforce the Code of Conduct in good
|
65
|
+
faith may face temporary or permanent repercussions as determined by other
|
66
|
+
members of the project's leadership.
|
67
|
+
|
68
|
+
## Attribution
|
69
|
+
|
70
|
+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
|
71
|
+
available at [http://contributor-covenant.org/version/1/4][version]
|
72
|
+
|
73
|
+
[homepage]: http://contributor-covenant.org
|
74
|
+
[version]: http://contributor-covenant.org/version/1/4/
|
data/Gemfile
ADDED
data/Gemfile.lock
ADDED
@@ -0,0 +1,24 @@
|
|
1
|
+
PATH
|
2
|
+
remote: .
|
3
|
+
specs:
|
4
|
+
jiff-date_range (0.0.1alpha)
|
5
|
+
|
6
|
+
GEM
|
7
|
+
remote: https://rubygems.org/
|
8
|
+
specs:
|
9
|
+
minitest (5.11.3)
|
10
|
+
rake (10.5.0)
|
11
|
+
timecop (0.9.1)
|
12
|
+
|
13
|
+
PLATFORMS
|
14
|
+
ruby
|
15
|
+
|
16
|
+
DEPENDENCIES
|
17
|
+
bundler (~> 2.0)
|
18
|
+
jiff-date_range!
|
19
|
+
minitest (~> 5.0)
|
20
|
+
rake (~> 10.0)
|
21
|
+
timecop (~> 0.9)
|
22
|
+
|
23
|
+
BUNDLED WITH
|
24
|
+
2.0.1
|
data/LICENSE.txt
ADDED
@@ -0,0 +1,21 @@
|
|
1
|
+
The MIT License (MIT)
|
2
|
+
|
3
|
+
Copyright (c) 2019 Rui Baltazar
|
4
|
+
|
5
|
+
Permission is hereby granted, free of charge, to any person obtaining a copy
|
6
|
+
of this software and associated documentation files (the "Software"), to deal
|
7
|
+
in the Software without restriction, including without limitation the rights
|
8
|
+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
9
|
+
copies of the Software, and to permit persons to whom the Software is
|
10
|
+
furnished to do so, subject to the following conditions:
|
11
|
+
|
12
|
+
The above copyright notice and this permission notice shall be included in
|
13
|
+
all copies or substantial portions of the Software.
|
14
|
+
|
15
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
16
|
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
17
|
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
18
|
+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
19
|
+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
20
|
+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
|
21
|
+
THE SOFTWARE.
|
data/README.md
ADDED
@@ -0,0 +1,116 @@
|
|
1
|
+
# DateRange
|
2
|
+
|
3
|
+
This gem came up from the need of using date ranges in our reporting tool
|
4
|
+
and the lack of a gem that actually provided date ranges manipulations, such as
|
5
|
+
building arrays of dates.
|
6
|
+
|
7
|
+
Furthermore, the logic for date manipulation within a date range is not always
|
8
|
+
clear as we have leap years and months with 28/29/30/31 days.
|
9
|
+
Though Ruby provides date shifting with `date >> 1` (date + 1.month) or
|
10
|
+
`date << 1` (date - 1.month) there are edge cases that would break the date
|
11
|
+
range from my point of view.
|
12
|
+
|
13
|
+
For example (please note this is not valid ruby code but a pseudo example)
|
14
|
+
|
15
|
+
```
|
16
|
+
d1 = Date.parse('31/01/2019')
|
17
|
+
d2 = Date.parse('30/04/2019')
|
18
|
+
|
19
|
+
monthly_stepped = []
|
20
|
+
current_date = d1
|
21
|
+
while current_date <= d2
|
22
|
+
monthly_stepped << current_date
|
23
|
+
current_date = current_date >> 1
|
24
|
+
end
|
25
|
+
```
|
26
|
+
I would expect my `monthly_stepped` to have the following dates
|
27
|
+
`[2019-01-31, 2019-02-28, 2019-03-31, 2019-04-30]`
|
28
|
+
and instead the result of this is the following
|
29
|
+
`[2019-01-31, 2019-02-28, 2019-03-28, 2019-04-28]`
|
30
|
+
|
31
|
+
I don't necessarily think that the ruby implementation is wrong, it simply does
|
32
|
+
not apply to my needs.
|
33
|
+
|
34
|
+
## Installation
|
35
|
+
|
36
|
+
Add this line to your application's Gemfile:
|
37
|
+
|
38
|
+
```ruby
|
39
|
+
gem 'jiff-date_range'
|
40
|
+
```
|
41
|
+
|
42
|
+
And then execute:
|
43
|
+
|
44
|
+
$ bundle
|
45
|
+
|
46
|
+
Or install it yourself as:
|
47
|
+
|
48
|
+
$ gem install jiff-date_range
|
49
|
+
|
50
|
+
## Usage
|
51
|
+
|
52
|
+
### Initialize a new date range
|
53
|
+
|
54
|
+
At the moment, this DateRange is expecting two dates to be passed in as argument
|
55
|
+
In the near future the ability to pass in other valid objects will most likely be
|
56
|
+
supported.
|
57
|
+
|
58
|
+
```ruby
|
59
|
+
d1 = Date.parse('27/02/2019')
|
60
|
+
d2 = Date.parse('03/03/2019')
|
61
|
+
date_range = Jiff::DateRange.new(d1, d2)
|
62
|
+
```
|
63
|
+
|
64
|
+
### by_month
|
65
|
+
|
66
|
+
This gives you the dates that fall within the date range in a monthly step. I
|
67
|
+
believe its easier if you see examples rather than describing them, so here they
|
68
|
+
are. Please note that the returning objects will be Date objects as well
|
69
|
+
|
70
|
+
```ruby
|
71
|
+
d1 = Date.parse('01/01/2019')
|
72
|
+
d2 = Date.parse('03/03/2019')
|
73
|
+
date_range = Jiff::DateRange.new(d1, d2)
|
74
|
+
date_range.by_month # => [01/01/2019, 01/02/2019, 01/03/2019]
|
75
|
+
```
|
76
|
+
|
77
|
+
```ruby
|
78
|
+
d1 = Date.parse('06/04/2019') - 60
|
79
|
+
d2 = Date.parse('06/04/2019')
|
80
|
+
date_range = Jiff::DateRange.new(d1, d2)
|
81
|
+
date_range.by_month # => [05/02/2019, 05/03/2019, 05/04/2019]
|
82
|
+
```
|
83
|
+
|
84
|
+
```ruby
|
85
|
+
d1 = Date.parse('30/01/2019')
|
86
|
+
d2 = Date.parse('03/04/2019')
|
87
|
+
date_range = Jiff::DateRange.new(d1, d2)
|
88
|
+
date_range.by_month # => [30/01/2019, 28/02/2019, 30/03/2019]
|
89
|
+
```
|
90
|
+
|
91
|
+
```ruby
|
92
|
+
d1 = Date.parse('31/01/2019')
|
93
|
+
d2 = Date.parse('29/04/2019')
|
94
|
+
date_range = Jiff::DateRange.new(d1, d2)
|
95
|
+
date_range.by_month # => [31/01/2019, 28/02/2019, 31/03/2019]
|
96
|
+
```
|
97
|
+
|
98
|
+
## Contributing
|
99
|
+
|
100
|
+
Bug reports and pull requests are welcome on GitHub at
|
101
|
+
https://github.com/rpbaltazar/jiff-date_range. This project is intended to be a
|
102
|
+
safe, welcoming space for collaboration, and contributors are expected to adhere
|
103
|
+
to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
|
104
|
+
As you'll understand because this is used for a production use case, it might be
|
105
|
+
a bit opinionated, but I'm definitely open for discussion as this is
|
106
|
+
an open topic.
|
107
|
+
|
108
|
+
## License
|
109
|
+
|
110
|
+
The gem is available as open source under the terms of the
|
111
|
+
[MIT License](https://opensource.org/licenses/MIT).
|
112
|
+
|
113
|
+
## Code of Conduct
|
114
|
+
|
115
|
+
Everyone interacting in the Jiff::DateRange project’s codebases, issue trackers,
|
116
|
+
chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/rpbaltazar/jiff-date_range/blob/master/CODE_OF_CONDUCT.md).
|
data/Rakefile
ADDED
data/TODO
ADDED
@@ -0,0 +1 @@
|
|
1
|
+
https://github.com/everypolitician/date_range/blob/master/test/date_range_test.rb
|
data/bin/console
ADDED
@@ -0,0 +1,14 @@
|
|
1
|
+
#!/usr/bin/env ruby
|
2
|
+
|
3
|
+
require "bundler/setup"
|
4
|
+
require "date_range"
|
5
|
+
|
6
|
+
# You can add fixtures and/or initialization code here to make experimenting
|
7
|
+
# with your gem easier. You can also use a different console, if you like.
|
8
|
+
|
9
|
+
# (If you use this, don't forget to add pry to your Gemfile!)
|
10
|
+
# require "pry"
|
11
|
+
# Pry.start
|
12
|
+
|
13
|
+
require "irb"
|
14
|
+
IRB.start(__FILE__)
|
data/bin/setup
ADDED
@@ -0,0 +1,36 @@
|
|
1
|
+
lib = File.expand_path('lib', __dir__)
|
2
|
+
|
3
|
+
$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
|
4
|
+
require 'jiff/date_range/version'
|
5
|
+
|
6
|
+
Gem::Specification.new do |spec|
|
7
|
+
spec.name = 'jiff-date_range'
|
8
|
+
spec.version = Jiff::DateRange::VERSION
|
9
|
+
spec.authors = ['Rui Baltazar']
|
10
|
+
spec.email = ['rui.p.baltazar@gmail.com']
|
11
|
+
|
12
|
+
spec.summary = "Date Range implementation based on Ruby's Date"
|
13
|
+
spec.description = 'Most Date Range implementations found, are either '\
|
14
|
+
'incomplete or rely on rails methods to work. This is '\
|
15
|
+
'intended to be used and work both in Ruby or Rails'
|
16
|
+
|
17
|
+
spec.homepage = 'https://github.com/rpbaltazar/jiff-date_range'
|
18
|
+
spec.license = 'MIT'
|
19
|
+
|
20
|
+
# Specify which files should be added to the gem when it is released.
|
21
|
+
# The `git ls-files -z` loads the files in the RubyGem
|
22
|
+
# that have been added into git.
|
23
|
+
spec.files = Dir.chdir(File.expand_path(__dir__)) do
|
24
|
+
`git ls-files -z`.split("\x0").reject do |f|
|
25
|
+
f.match(%r{^(test|spec|features)/})
|
26
|
+
end
|
27
|
+
end
|
28
|
+
spec.bindir = 'exe'
|
29
|
+
spec.executables = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
|
30
|
+
spec.require_paths = ['lib']
|
31
|
+
|
32
|
+
spec.add_development_dependency 'bundler', '~> 2.0'
|
33
|
+
spec.add_development_dependency 'minitest', '~> 5.0'
|
34
|
+
spec.add_development_dependency 'rake', '~> 10.0'
|
35
|
+
spec.add_development_dependency 'timecop', '~> 0.9'
|
36
|
+
end
|
@@ -0,0 +1,62 @@
|
|
1
|
+
require 'date'
|
2
|
+
|
3
|
+
require_relative 'date_range/version'
|
4
|
+
require_relative 'month_mapper'
|
5
|
+
|
6
|
+
module Jiff
|
7
|
+
class DateRange
|
8
|
+
attr_reader :start_date
|
9
|
+
attr_reader :end_date
|
10
|
+
|
11
|
+
def initialize(start_date, end_date)
|
12
|
+
@start_date = start_date
|
13
|
+
@end_date = end_date
|
14
|
+
end
|
15
|
+
|
16
|
+
def by_month
|
17
|
+
return month_ends_in_range if date_is_end_of_month(@start_date)
|
18
|
+
|
19
|
+
dates = []
|
20
|
+
current_date = @start_date
|
21
|
+
while current_date <= @end_date
|
22
|
+
dates << current_date
|
23
|
+
current_date = next_date(current_date, dates)
|
24
|
+
end
|
25
|
+
dates
|
26
|
+
end
|
27
|
+
|
28
|
+
def to_a
|
29
|
+
date_range.to_a
|
30
|
+
end
|
31
|
+
|
32
|
+
private
|
33
|
+
|
34
|
+
def days_grouped_by_month
|
35
|
+
to_a.group_by { |date| "#{date.month}-#{date.year}" }
|
36
|
+
end
|
37
|
+
|
38
|
+
def month_ends_in_range
|
39
|
+
dates = days_grouped_by_month.values.map(&:last)
|
40
|
+
dates.pop unless date_is_end_of_month(@end_date)
|
41
|
+
dates
|
42
|
+
end
|
43
|
+
|
44
|
+
def next_date(current_date, dates)
|
45
|
+
# NOTE: If first date is in february, then there is no problem
|
46
|
+
# in jumping forward.
|
47
|
+
if current_date.month == 2 && dates.length > 1
|
48
|
+
dates[-2] >> 2
|
49
|
+
else
|
50
|
+
current_date >> 1
|
51
|
+
end
|
52
|
+
end
|
53
|
+
|
54
|
+
def date_range
|
55
|
+
(@start_date..@end_date)
|
56
|
+
end
|
57
|
+
|
58
|
+
def date_is_end_of_month(date)
|
59
|
+
date.day == MonthMapper.days_in_month(date.month)
|
60
|
+
end
|
61
|
+
end
|
62
|
+
end
|
@@ -0,0 +1,25 @@
|
|
1
|
+
module Jiff
|
2
|
+
module MonthMapper
|
3
|
+
DAYS_MONTH = {
|
4
|
+
1 => 31,
|
5
|
+
2 => nil,
|
6
|
+
3 => 31,
|
7
|
+
4 => 30,
|
8
|
+
5 => 31,
|
9
|
+
6 => 30,
|
10
|
+
7 => 31,
|
11
|
+
8 => 31,
|
12
|
+
9 => 30,
|
13
|
+
10 => 31,
|
14
|
+
11 => 30,
|
15
|
+
12 => 31
|
16
|
+
}.freeze
|
17
|
+
|
18
|
+
def self.days_in_month(month, leap = false)
|
19
|
+
return DAYS_MONTH[month] unless month == 2
|
20
|
+
return 29 if leap
|
21
|
+
|
22
|
+
28
|
23
|
+
end
|
24
|
+
end
|
25
|
+
end
|
@@ -0,0 +1 @@
|
|
1
|
+
require_relative 'jiff/date_range'
|
metadata
ADDED
@@ -0,0 +1,116 @@
|
|
1
|
+
--- !ruby/object:Gem::Specification
|
2
|
+
name: jiff-date_range
|
3
|
+
version: !ruby/object:Gem::Version
|
4
|
+
version: 0.0.1alpha
|
5
|
+
platform: ruby
|
6
|
+
authors:
|
7
|
+
- Rui Baltazar
|
8
|
+
autorequire:
|
9
|
+
bindir: exe
|
10
|
+
cert_chain: []
|
11
|
+
date: 2019-04-06 00:00:00.000000000 Z
|
12
|
+
dependencies:
|
13
|
+
- !ruby/object:Gem::Dependency
|
14
|
+
name: bundler
|
15
|
+
requirement: !ruby/object:Gem::Requirement
|
16
|
+
requirements:
|
17
|
+
- - "~>"
|
18
|
+
- !ruby/object:Gem::Version
|
19
|
+
version: '2.0'
|
20
|
+
type: :development
|
21
|
+
prerelease: false
|
22
|
+
version_requirements: !ruby/object:Gem::Requirement
|
23
|
+
requirements:
|
24
|
+
- - "~>"
|
25
|
+
- !ruby/object:Gem::Version
|
26
|
+
version: '2.0'
|
27
|
+
- !ruby/object:Gem::Dependency
|
28
|
+
name: minitest
|
29
|
+
requirement: !ruby/object:Gem::Requirement
|
30
|
+
requirements:
|
31
|
+
- - "~>"
|
32
|
+
- !ruby/object:Gem::Version
|
33
|
+
version: '5.0'
|
34
|
+
type: :development
|
35
|
+
prerelease: false
|
36
|
+
version_requirements: !ruby/object:Gem::Requirement
|
37
|
+
requirements:
|
38
|
+
- - "~>"
|
39
|
+
- !ruby/object:Gem::Version
|
40
|
+
version: '5.0'
|
41
|
+
- !ruby/object:Gem::Dependency
|
42
|
+
name: rake
|
43
|
+
requirement: !ruby/object:Gem::Requirement
|
44
|
+
requirements:
|
45
|
+
- - "~>"
|
46
|
+
- !ruby/object:Gem::Version
|
47
|
+
version: '10.0'
|
48
|
+
type: :development
|
49
|
+
prerelease: false
|
50
|
+
version_requirements: !ruby/object:Gem::Requirement
|
51
|
+
requirements:
|
52
|
+
- - "~>"
|
53
|
+
- !ruby/object:Gem::Version
|
54
|
+
version: '10.0'
|
55
|
+
- !ruby/object:Gem::Dependency
|
56
|
+
name: timecop
|
57
|
+
requirement: !ruby/object:Gem::Requirement
|
58
|
+
requirements:
|
59
|
+
- - "~>"
|
60
|
+
- !ruby/object:Gem::Version
|
61
|
+
version: '0.9'
|
62
|
+
type: :development
|
63
|
+
prerelease: false
|
64
|
+
version_requirements: !ruby/object:Gem::Requirement
|
65
|
+
requirements:
|
66
|
+
- - "~>"
|
67
|
+
- !ruby/object:Gem::Version
|
68
|
+
version: '0.9'
|
69
|
+
description: Most Date Range implementations found, are either incomplete or rely
|
70
|
+
on rails methods to work. This is intended to be used and work both in Ruby or Rails
|
71
|
+
email:
|
72
|
+
- rui.p.baltazar@gmail.com
|
73
|
+
executables: []
|
74
|
+
extensions: []
|
75
|
+
extra_rdoc_files: []
|
76
|
+
files:
|
77
|
+
- ".gitignore"
|
78
|
+
- ".travis.yml"
|
79
|
+
- CODE_OF_CONDUCT.md
|
80
|
+
- Gemfile
|
81
|
+
- Gemfile.lock
|
82
|
+
- LICENSE.txt
|
83
|
+
- README.md
|
84
|
+
- Rakefile
|
85
|
+
- TODO
|
86
|
+
- bin/console
|
87
|
+
- bin/setup
|
88
|
+
- jiff-date_range.gemspec
|
89
|
+
- lib/jiff-date_range.rb
|
90
|
+
- lib/jiff/date_range.rb
|
91
|
+
- lib/jiff/date_range/version.rb
|
92
|
+
- lib/jiff/month_mapper.rb
|
93
|
+
homepage: https://github.com/rpbaltazar/jiff-date_range
|
94
|
+
licenses:
|
95
|
+
- MIT
|
96
|
+
metadata: {}
|
97
|
+
post_install_message:
|
98
|
+
rdoc_options: []
|
99
|
+
require_paths:
|
100
|
+
- lib
|
101
|
+
required_ruby_version: !ruby/object:Gem::Requirement
|
102
|
+
requirements:
|
103
|
+
- - ">="
|
104
|
+
- !ruby/object:Gem::Version
|
105
|
+
version: '0'
|
106
|
+
required_rubygems_version: !ruby/object:Gem::Requirement
|
107
|
+
requirements:
|
108
|
+
- - ">"
|
109
|
+
- !ruby/object:Gem::Version
|
110
|
+
version: 1.3.1
|
111
|
+
requirements: []
|
112
|
+
rubygems_version: 3.0.3
|
113
|
+
signing_key:
|
114
|
+
specification_version: 4
|
115
|
+
summary: Date Range implementation based on Ruby's Date
|
116
|
+
test_files: []
|