* tick.interval.bounds function is now consistent for years, year-mon…

…ths and dates in setting the `end` to be inclusive

* Strings are no longer accepted as beginning/end when constructing an interval
* Strings are no longer accepted as arguments to clock

CHANGELOG

@@ -1,3 +1,9 @@
+# 0.7.0
+
+* tick.interval.bounds function is now consistent for years, year-months and dates in setting the `end` to be inclusive
+* Strings are no longer accepted as beginning/end when constructing an interval
+* Strings are no longer accepted as arguments to clock
+
 # 0.6.1 
 
 Add equivalents of clojure.core's max-key and min-key 

docs/index.html

@@ -2459,7 +2459,7 @@ <h2 id="_intervals">7. Intervals</h2>
 <p>Intervals are maps containing both a <code>tick/beginning</code> and a <code>tick/end</code> entry. This flexible design allows any Clojure map to be treated as an interval.</p>
 </div>
 <div class="paragraph">
-<p>Intervals can be represented two local times as well as instants.</p>
+<p>The start and end of an interval should have the same type.</p>
 </div>
 <div class="paragraph">
 <p>Interval functions are currently alpha status and so reside in the <code>tick.alpha.interval</code> namespace, rather than the
@@ -2485,8 +2485,8 @@ <h3 id="_construction_4">7.1. Construction</h3>
 </div>
 <div class="listingblock code">
 <div class="content">
-<pre class="highlight"><code class="language-clojure" data-lang="clojure">{:tick/beginning "2018-12-31T23:55:00Z"
- :tick/end "2019-01-01T00:00:00Z"}</code></pre>
+<pre class="highlight"><code class="language-clojure" data-lang="clojure">{:tick/beginning (t/instant "2018-12-31T23:55:00Z")
+ :tick/end (t/instant "2019-01-01T00:00:00Z"})</code></pre>
 </div>
 </div>
 </div>
@@ -2509,7 +2509,7 @@ <h3 id="_construction_4">7.1. Construction</h3>
 <div class="sect2">
 <h3 id="_derivation_3">7.2. Derivation</h3>
 <div class="paragraph">
-<p>Dates, months and years can also be considered to be themselves ranges, and can be converted to intervals with the <code>t.i/bounds</code> function.</p>
+<p>Dates, months and years can also be considered to be themselves ranges, and can be converted to intervals with the <code>t.i/bounds</code> function. The start and end are both inclusive. This means for example that the <code>end</code> of one day <code>meets</code> the start of the next day.</p>
 </div>
 <div class="exampleblock">
 <div class="content">

docs/intervals.adoc

@@ -4,7 +4,7 @@ In _tick_, an interval is a span of time defined by two points in time, the firs
 
 Intervals are maps containing both a `tick/beginning` and a `tick/end` entry. This flexible design allows any Clojure map to be treated as an interval.
 
-Intervals can be represented two local times as well as instants.
+The start and end of an interval should have the same type.
 
 Interval functions are currently alpha status and so reside in the `tick.alpha.interval` namespace, rather than the 
 main `tick.core` namespace.
@@ -24,8 +24,8 @@ Here we use a literal map syntax to construct an interval representing the last
 
 [source.code,clojure]
 ----
-{:tick/beginning "2018-12-31T23:55:00Z"
- :tick/end "2019-01-01T00:00:00Z"}
+{:tick/beginning (t/instant "2018-12-31T23:55:00Z")
+ :tick/end (t/instant "2019-01-01T00:00:00Z"})
 ----
 
 ====
@@ -43,7 +43,7 @@ Alternatively, we can use the `t.i/new-interval` function which takes the two bo
 
 == Derivation
 
-Dates, months and years can also be considered to be themselves ranges, and can be converted to intervals with the `t.i/bounds` function.
+Dates, months and years can also be considered to be themselves ranges, and can be converted to intervals with the `t.i/bounds` function. The start and end are both inclusive. This means for example that the `end` of one day `meets` the start of the next day.
 
 ====
 To return today as an interval: