Skip to content
Adam Frey edited this page Jul 31, 2017 · 4 revisions

Unrepl has no extension mechanism for now. The protocol itself is very open, but short of forking the implementation and creating a new blob, there's no way to extend the implementation.

There are several kinds of extensions:

  • new tooling commands (completion for example) that don't interact with the user REPL streams
  • REPL mods (eg participating in :caught or :print)
  • others?

Orthogonal to that is how code is loaded (blob, side-loading etc.) and how it is munged.

A possibility to extend unrepl would be exposing a stable var to start a nested unrepl with slightly modified options. This could maybe make for a small yet powerful API (compared to, for example, a lot of register-this-and-that!).