time_math2 0.0.3 → 0.0.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 006dfa63a22116ad083fd98e2aca4390734bce26
-  data.tar.gz: 028d5e1ca0a36f80840b95aadb675f60497385f5
+  metadata.gz: 76771d4aa5435a2100af858a4bd4851ef81d35c9
+  data.tar.gz: 23abf05b1c0b3dd19a6552619cda98e360b73840
 SHA512:
-  metadata.gz: 261cbba1b37663d18b456edfb0f0ea7a18dbd7c78c72d4c77d6d20feb664a90f4ca2baaffcaf7493a04181cf37c40a4c3480e2493dd767d4dece3dcdf0271e37
-  data.tar.gz: 2d9beccf3cd5e3a3b4f7a35366ec20576dc770c7570768cc6784b8cfb0bcc139df713ac88ac764ba2eb2eb44b6c4aa070d6c3b1e20626bb5c58540a38eff991b
+  metadata.gz: a314061838072dac1c4bec199a7a1128f74732a3a0cc041996674e1b6d91a35b53cdd7f7800a9b187108afd73d03027e4e6776c9c5b53f3393df06b2f13d0231
+  data.tar.gz: 192e2f2f194d52dc4d39868ccae10d83bab53350b63177725c3677c2e607574463420d62eab0c6151741747a1a0fe44de408cc103713319d3de607907ef8bf9e

data/README.md

@@ -208,81 +208,6 @@ it means:
   it is preserved by TimeMath (but be careful about jumping around DST,
   offset would not change).
 
-
-## Time series generation: "laces"
-
-I'm a real fan of funny names in gems. Here we have time **boots** for working
-with time **steps**. So, something continuous will be called **lace**.
-
-I hope, next examples are pretty self-explanatory.
-
-```ruby
-from = Time.parse('2015-03-05 10:08')
-to = Time.parse('2015-03-09 11:07')
-
-lace = TimeBoots.month.lace(from, to)
-# => #<TimeBoots::Lace(2015-03-05 10:08:00 +0200 - 2015-03-09 11:07:00 +0200)>
-
-# or
-TimeBoots.lace(:month, from, to)
-# => #<TimeBoots::Lace(2015-03-05 10:08:00 +0200 - 2015-03-09 11:07:00 +0200)>
-
-lace.pull
-# => [2015-03-05 10:08:00 +0200,
-#     2015-03-06 10:08:00 +0200,
-#     2015-03-07 10:08:00 +0200,
-#     2015-03-08 10:08:00 +0200,
-#     2015-03-09 10:08:00 +0200]
-```
-
-So, we have just a series of times, each day, from `from` until `to`.
-Note, there is a same time of the day (10:08), as it was in `from`.
-
-The `pull` method has an optional argument, when it is `true`, the
-method returns `floor`-ed times (e.g. midnights for daily lace):
-
-```ruby
-lace.pull(true)
-# => [2015-03-05 10:08:00 +0200,
-#     2015-03-06 00:00:00 +0200,
-#     2015-03-07 00:00:00 +0200,
-#     2015-03-08 00:00:00 +0200,
-#     2015-03-09 00:00:00 +0200]
-```
-
-Note the first value still at 10:08: we don't want to go before `from`.
-Lace also can "expand" your period for you (`floor` the beginning and
-`ceil` the end):
-
-```ruby
-lace.expand
-# => #<TimeBoots::Lace(2015-03-05 00:00:00 +0200-2015-03-10 00:00:00 +0200)>
-
-# or
-lace.expand!
-
-# or start with expanded:
-TimeBoots.month.lace(from, to, expanded: true)
-```
-
-Another useful lace's functionality is generating periods.
-It can be useful for filtering daily data from database, for example:
-
-```ruby
-lace.pull_ranges
-# => [2015-03-05 10:08:00 +0200...2015-03-06 10:08:00 +0200,
-#     2015-03-06 10:08:00 +0200...2015-03-07 10:08:00 +0200,
-#     2015-03-07 10:08:00 +0200...2015-03-08 10:08:00 +0200,
-#     2015-03-08 10:08:00 +0200...2015-03-09 10:08:00 +0200,
-#     2015-03-09 10:08:00 +0200...2015-03-09 11:07:00 +0200]
-
-# Now, you can do something like:
-
-lace.pull_ranges.map{|range| dataset.where(timestamp: range).count}
-# ...and have your daily stats with one line of code
-
-```
-
 ## Got it, what else?
 
 TimeMath also play well when included into other classes or modules:

data/lib/time_math/version.rb

@@ -1,4 +1,4 @@
 module TimeMath
   # @private
-  VERSION = '0.0.3'.freeze
+  VERSION = '0.0.4'.freeze
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: time_math2
 version: !ruby/object:Gem::Version
-  version: 0.0.3
+  version: 0.0.4
 platform: ruby
 authors:
 - Victor Shepelev