If you can model the authentication process as a state machine, have a pure
function which accepts auth-state and data and returns either a new state
or an operation to get new data to determine the next state.
E.g. (next-auth-state {:stage :not-authed :login "login" :password "pass"}
nil) =>
Library for helping print things prettily, in Clojure - ANSI fonts,
formatted exceptions
To get around Clojure 1.8 deep linking,
io.aviso.repl/install-pretty-exceptions now reloads clojure.test
after overriding other functions (such as
clojure.stacktrace/print-stack-trace). This problem
Hi Varun - the best advice I think I could give you is to spend a
whole bunch of time on https://clojuredocs.org and https://www.conj.io
(any others?) familiarising yourself with the core API. There is also
the official http://clojure.org/api/api but I find the example on
clojuredocs invaluable.
I had a recent misadventure trying to configure Leiningen to sign releases
and/or tags with a side-helping of a minor clash with Git Flow.
It turned out to be a convoluted process and I couldn't find a clear guide
to my setup, which I assume is a fairly common one, so I wrote one:
Hi,
Currently, I am in the process of writing a client to server API which is
not trivial to consume. In particular it needs a 3-step authentication
process: login with user name and password, get an authentication token,
open a session with the token and finally consume the API with the
