This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-04-08
Channels
- # announcements (8)
- # aws (2)
- # babashka (11)
- # babashka-sci-dev (39)
- # beginners (62)
- # calva (5)
- # cider (1)
- # clj-kondo (50)
- # cljdoc (2)
- # cljs-dev (6)
- # clojure (52)
- # clojure-austin (22)
- # clojure-czech (13)
- # clojure-europe (88)
- # clojure-nl (1)
- # clojure-norway (5)
- # clojure-uk (6)
- # clojuredesign-podcast (13)
- # clojurescript (45)
- # community-development (3)
- # core-typed (31)
- # cursive (12)
- # datahike (2)
- # datalevin (7)
- # datomic (5)
- # events (1)
- # exercism (11)
- # fulcro (27)
- # gratitude (1)
- # holy-lambda (3)
- # hoplon (2)
- # introduce-yourself (2)
- # jobs (1)
- # lambdaisland (3)
- # lsp (110)
- # malli (2)
- # meander (4)
- # music (2)
- # off-topic (50)
- # overtone (1)
- # pathom (13)
- # polylith (26)
- # re-frame (4)
- # releases (2)
- # rewrite-clj (3)
- # ring (12)
- # shadow-cljs (20)
- # specter (4)
- # tools-deps (8)
- # xtdb (40)
Typed Clojure 1.0.26 - Extensive improvements, including:
- support reify
, satisfies
in Clojure
- support defprotocol
, implements?
in ClojureScript
- support annotating composite predicates like (defn sym-or-kw? [a] (or (symbol? a) (keyword? a)))
https://www.patreon.com/posts/64869793

Clay (version 1-alpha1
) is a new little attempt to provide some of the visual tooling needs of the emerging data-science stack and community.
https://scicloj.github.io/clay/#/notebooks/intro.clj
It has been growing gradually as a series of small experiments in the #visual-tools group.
In the last couple of years, a few of us have been using Notespace for documentation (literate programming), data exploration, study groups, workshops, etc.
With the emergence of amazing tools such at Portal and Clerk, which are getting lots of attention from both users and maintainers, it seems to make sense to put Notespace on hold, and rely on those amazing tools (and others).
Clay tries to maintain a bit of the Notespace approach, mostly regarding dynamic interaction and way of expression (using the Kindly library), but implement it as a thin convenience layer on top of other tools, allowing one to use the full power of those tools where appropriate.
Lots of Clay's (& Kindly's) attention is around creating a compatibility layer, which allows one to use the same code and render it visually in different tools. This made it possibly, for example, to port the documentation of Viz.clj from Notespace to Clerk (wrapped by Clay) with no code change:
https://scicloj.github.io/viz.clj/#/notebooks/intro.clj
This is still considered experimental. Please share your feedback.
Many thanks to @clark.thomaswilliam, who has been involved in testing and designing the usability aspects (and exploring some implementation details),
to @djblue, @mkvlr, @jackrusher, @philippmarkovics for their patient and wise support with the brilliant tooling they are creating,
to Rohit Thadani and @ezmiller77 for further testing and feedback,
and to the #visual-tools group, which has been supporting and hosting this exploration so far.
(image credit: Wikimedia Commons)
clj-kondo v2022.04.08 - static analyzer and linter for Clojure code that sparks joy! āØ
ā¢ https://github.com/clj-kondo/clj-kondo/issues/1331: new linter :non-arg-vec-return-type-hint
that warns when a return type hint is not placed on the arg vector (CLJ only). See https://github.com/clj-kondo/clj-kondo/blob/master/doc/linters.md#non-arg-vec-return-type-hint.
ā¢ Enable :namespace-name-mismatch
by default
ā¢ https://github.com/clj-kondo/clj-kondo/pull/1611: support ^:replace
override for nested config values
ā¢ https://github.com/clj-kondo/clj-kondo/issues/1625: Add option --skip-lint
, to skip linting while still executing other tasks like copying configuration with --copy-configs
.
ā¢ https://github.com/clj-kondo/clj-kondo/issues/1620: return type too narrow for re-find
Analysis:
ā¢ https://github.com/clj-kondo/clj-kondo/issues/1623: Implement analysis for Java classes: :java-class-definitions
and :java-class-usages
. See https://github.com/clj-kondo/clj-kondo/blob/master/analysis/README.md.
ā¢ https://github.com/clj-kondo/clj-kondo/pull/1635: add :end-row
and end-col
to analyze data for :namespace-definitions
ā¢ https://github.com/clj-kondo/clj-kondo/issues/1651: Improvements for :protocol-impls
ā¢ https://github.com/clj-kondo/clj-kondo/issues/1612: Improve analysis for deftype
ā¢ https://github.com/clj-kondo/clj-kondo/issues/1613: Improve analysis for reify
ā¢ https://github.com/clj-kondo/clj-kondo/issues/1609: keyword analysis for ns
+ require
channel: #clj-kondo

Nice. Btw. in https://github.com/clj-kondo/clj-kondo/blob/master/analysis/README.md I don't see anything about Java classes.
@U06BE1L6T Good point, these keys should be added here: https://github.com/clj-kondo/clj-kondo/blob/master/analysis/README.md#extra-analysis
It's just because there was See https://github.com/clj-kondo/clj-kondo/blob/master/analysis/README.md next to it so I thought I would have a look š.