This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-04-17
Channels
- # ai (115)
- # announcements (8)
- # babashka (26)
- # beginners (7)
- # biff (8)
- # calva (1)
- # cider (10)
- # clerk (2)
- # clj-together (11)
- # clojure (26)
- # clojure-boston (1)
- # clojure-denmark (3)
- # clojure-europe (23)
- # clojure-nl (1)
- # clojure-norway (33)
- # clojure-uk (3)
- # clojurescript (14)
- # conjure (3)
- # cursive (65)
- # emacs (10)
- # events (18)
- # exercism (6)
- # honeysql (14)
- # hyperfiddle (11)
- # kaocha (6)
- # nbb (17)
- # off-topic (58)
- # pathom (5)
- # reagent (28)
- # reitit (1)
- # releases (1)
- # sci (3)
- # shadow-cljs (22)
- # xtdb (29)
Another feature I'm working on is adding a SCI context to the online coding editor, to make it a proper Clojure coding environment rather than a glorified test runner.
This is an interesting problem, because Exercism is an existing Ruby on Rails app, with a React frontend. So the challenge has been just figuring out, how to ship it in the least "invasive" way, in a non-Clojure environment
My first idea was to use scittle. The prototype works great! Though this is not really ideal, because it would need to be injected into the site's HTML or something, idek
So it finally hit me, to just go all the way and release a Codemirror plugin, as an npm package
Nextjournal already made one that I forked to use as a template: https://github.com/bobbicodes/clojure-eval/ all I need to do is bang on it until it does what I want
I'm still trying to determine if my reasoning is sound - I've created npm packages using nbb before, but never one in which the interpreter is available at runtime