mogge 😼

Morning

o/

morning

morning

ahoy hoy

månmån

morning

Bore da

still working?

on holidays - just now poking my laptop

(= (+ 👶 holiday) "Does not compute")

@jasonbell you play the chapman stick?

I do

Quite an unusual instrument to get into

Is that from an interest in prog? Jazz?

@alex.lynham I went the fairly standard route of Peter Gabriel -> King Crimson -> David Sylvian 🙂

My friend and teacher is more the jazzer.

@korny just catching up with this channel and seeing your question posted earlier this week. I'm not convinced the following would help you but just in case. Not too long ago I've worked on a command line tool to predict the impact of graphql query changes on underlying backends. The idea was to get some config data from a local file (edn and/or excel), get data from a development graphql server spitting out query results + instrumentation data such as backends being hit, query github API to retrieve queries within .graphql files, aggregate instrumentation data across these queries, all this to spit out some edn report detailing overall impact on backends and delta compared to previous run. I started with clj because of docjure (excel reporting was the initial idea). However depending on how things were going it could remain a cli only thing to be included as part of CI (in which case cljs startup time and edn are better fit), or become a constantly running service with some proper reporting UX (in which case clj and edn were fine). So I spent a lot of time converting my initial clj+excel code into cljc+edn, replacing clj only libs with cljc ones and keeping reader conditionals within lower utility namespaces. In the end I moved to a different team and stopped working on this. I did not want my cljc work to go into oblivion even for my own sake. So I extracted the more generic part into this library: https://github.com/fmjrey/cameleon I know a simple cli logic was one of your initial question. Unfortunately I did not extract the cli logic because it was part of core.cljc along with a several reader conditionals to deal with tools.cli and its cljs counterpart. But a lot of concerns regarding http io, rest io, file io, edn io, test fixtures built from http recording, http client mocking, have been extracted and could be of interest.