Skip to content
master
Switch branches/tags
Code

Latest commit

 

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
 
 
 
 
bin
 
 
dev
 
 
 
 
src
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

tick

A Clojure(Script) library for dealing with time. Intended as a replacement for clj-time.

Based on Java 8 time (on the JVM) and js-joda (on JavaScript runtimes). We are considering an implementation based on Temporal, via Tempo when it is available.

(require '[tick.alpha.api :as t])

;; Get the current time
(t/now)

Status

Alpha: Ready to use with the caveat that the API might still undergo minor changes.

See the 1.0 checklist for what we think is needed for moving out of alpha - not that much.

Install

Get the latest from Clojars and add to your project.clj, build.boot or deps.edn.

Tick versions 0.4.24-alpha and up require minimum Clojurescript version of 1.10.741

For Clojurescript users of Tick, see docs/cljs.adoc, for some discussion around Clojurescript build size.

Here is a one-liner to drop into a node repl with tick:

clj -Sdeps '{:deps {org.clojure/clojurescript {:mvn/version "1.10.741" } tick {:mvn/version "0.4.24-alpha"} }}' -m cljs.main  -re node  --repl

Development

CircleCI

Develop The Documentation Site

Build the Cljs

make dev-docs-cljs

Build the html

make docs/index.html

Serve the docs directory and navigate to it in a browser

Develop Tick

Jack in with cider or equivalent method in other IDEs, and start the cljs build with:

(figwheel-start!)

And when you get a REPL you can run all the JVM tests with


(test-clj) ---

Or outside of the REPL run:

make test-all

which will run clojure, clojurescript (node) and clojurescript (chrome) tests. JVM tests are currently running with Kaocha while JS tests are using figwheel-main and the cljs-test-runner.

As long as you have you have started your repl with these aliases "-A:dev:test-clj", you can also run backend clojure tests in the repl with something like

(require '[kaocha.repl :as kr])
(kr/run :clj)

npm dependencies

For running the ClojureScript tests you will need the following npm dependencies installed:

sudo npm install -g karma-cli
sudo npm install -g karma
sudo npm install -g karma-chrome-launcher
sudo npm install -g karma-cljs-test

Check .circleci/config.yml for the versions that are known to work.

Setting CHROME_BIN

If you get an error similar to the following:

No binary for ChromeHeadless browser on your platform.

Set the environment variable CHROME_BIN to wherever Chrome or Chromium is installed on your platform.

Release

create a git tag.

make install VERSION=your-tag (this installs in ~/.m2 - check that things look ok)

make deploy VERSION=your-tag - you need to have set up clojars credentials as per https://github.com/applied-science/deps-library

git push origin new-tag-name

Documentation

Acknowledgements

In particular, special credit to Eric Evans for discovering Allen’s interval algebra and pointing out its potential usefulness, demonstrating a working implementation of Allen’s ideas in his Clojure library.

Thanks also to my esteemed colleagues Patrik Kårlin for his redesign of the interval constructor function, and Henry Widd for porting to cljc.

The MIT License (MIT)

Copyright © 2016-2021 JUXT LTD.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.