Proof-of-concept implementation for nREPL auto-discovered ops and corresponding client-side auto-generated commands.
For background, see this thread.
Currently implemented as an nrepl middleware with a reference
implementation of a toggle-trace nrepl operation using
tools.trace as well as an
operation for running clojure.test tests.
With the nrepl-discover.el elisp included, it's possible to run M-x nrepl-discover on an active nREPL session for this project, which
results in the creation of commands for every var which has
:nrepl/op metadata attached.
There are a few sample ops including toggle-trace and run-tests
which invoke tools.trace and clojure.test functionality
respectively. Once the discovery has run
For Emacs usage you would typically invoke nrepl-discover from
nrepl-connected-hook and define key bindings for
nrepl-toggle-trace and nrepl-run-tests, the latter of which should
be able to obsolete the clojure-test-mode library. The Emacs lisp
code is included as a reference implementation; the hope is that the
same functionality could be ported to other editors like Vim and
CounterClockwise.
Lots to do:
-
Figure out what response types to support beyond strings
-
file edits? (or just make the edit server-side and tell client to refresh)
-
what does the inspector need? (html? how do we represent hyperlink targets?)
-
Determine whose responsibility it is to load namespaces containing nrepl ops so they can be discovered.
-
Implement for other editors
-
Unload-ns op