This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # announcements (13)
- # aws (1)
- # bangalore-clj (4)
- # beginners (66)
- # boot (11)
- # calva (27)
- # cider (27)
- # clj-kondo (76)
- # cljdoc (6)
- # cljs-dev (38)
- # clojars (3)
- # clojure (143)
- # clojure-dev (2)
- # clojure-europe (6)
- # clojure-greece (10)
- # clojure-italy (10)
- # clojure-nl (5)
- # clojure-norway (2)
- # clojure-sweden (1)
- # clojure-uk (19)
- # clojurescript (49)
- # cursive (13)
- # datomic (14)
- # duct (6)
- # figwheel-main (3)
- # fulcro (31)
- # funcool (7)
- # jobs (3)
- # keechma (142)
- # liberator (1)
- # off-topic (15)
- # om (2)
- # reagent (1)
- # reitit (2)
- # remote-jobs (1)
- # rewrite-clj (73)
- # shadow-cljs (21)
- # spacemacs (18)
- # sql (5)
- # tools-deps (10)
- # yada (1)
FWIW I made a couple of clj-kondo specific tweaks to rewrite-clj which can be seen here: https://github.com/borkdude/clj-kondo/commits/master/parser/clj_kondo/impl/rewrite_clj
The first commit also contains the patch for namespaced maps, I didn't make that an explicit commit
Hi @borkdude, thanks for checking in! I am for now finished with my adventures in cljs, and am back to rewrite-cljc work.
While looking at the namespaced map issue you raised here I looked at your rewrite-clj fork - my compliments in your code, it is very easy to read.
I also took a first stab at docs. Based on an old chat in cljdoc channel, I am trying out asciidoc.
i've been trying asciidoc as well -- today i hit a bit of a snag -- i wrote a README for a repo for an issue and then was about to paste as issue when i learned that github issues don't appear to support asciidoc 😞 went through and rewrote as markdown...
github support for asciidoc is... partial... not horrible... but not wonderful. I am going to leave a minimimal README in markdown and the rest will be in asciidoc.
i was having a hard time with getting previews to work...finally have something tolerable
Yeah me too. @borkdude likes vscode for this. I’ve settled on a browser plugin that seems to work well.
@borkdude the issue you brought up with namespaced maps has led me to wonder what I really need to resolve for namespaced maps for
sexpr. Now that I’ve got the code to stop resolving when not using sexpr, I’m exploring the notion that the current sexpr code might be resolving when it does not have to. Anyways, thanks again for sharing the issue, it has helped!
although I don't use it, my patch does support
but I see your problem there. I cheated a little bit, by always using only one colon 😉
the information that it's an alias is stored when parsing though, and I leverage that in linting
well, for rewriting you could probably just emit a double colon again, but for sexpr it isn't sufficient
ah I see:
bar=> (require '[clj-kondo.impl.rewrite-clj.parser :as p]) nil bar=> (clj-kondo.impl.rewrite-clj.node/sexpr (p/parse-string "::foo")) :bar/foo
so maybe that makes sense. however, I ran into a bug while parsing, not while doing sexpr I think
but when resolving things like
::p/foo this should not crash when parsing or rewriting
I am musing that I might not need to resolve the p namespace alias, but have not had coffee yet.
I’ll carry on with my exploration and am looking forward to getting back to you after I am caffeinated.
Oh right, forgot to mention I am starting to look at clj-kondo warnings and even have my very first clj-kondo config! Very cool!
(i tried vscode with a couple of asciidoc extensions, but didn't succeed in getting them to work -- this was after trying some the browser plugin route. that also had problems...oddly enough for files with name "README.adoc"...anyway, now using asciidocfx w/ some success.)
I did have some success with vscode, but I prefer to stay in spacemacs. I found that spacemacs had some oddly teeny tiny default fonts for asciidocs and adjusted accordingly. The chrome browser plugin I am using had to be configured to render local files.
i had to stop using chromium because it refused to start up for me one day...now after quite some time i am back on firefox.
as long as we have strayed this far and since you appear to be using emacs...today i found what i think may be a hidden gem.
I mostly prefer firefox these days too. But did not get asciidoc plugin to work on firefox. I might gry harder.
it's a socket-repl-based clojure and cljs thing with a set of features that happens to be along the sorts of things i had been making...too bad i didn't find this some months back.
fwiw, i think i tried a firefox-based asciidoc plugin but it was the one that for some reason wouldn't preview files named "README.adoc"
the socket-repl part is important for having something that will work with jvm clojure, cljs, and clojure clr.
i had to stop using that a fair bit back for various reasons that probably don't apply for other folks -- so i'm not sure. depends on what you use from cider i guess 🙂
i found there were only a few things i really used for clojure work, so if your requirements are along those lines, it may be good enough.
i hope some day we get something with source that provides a complete debugging experience.
do you know of a rebl alternative for cljs? punk was getting closer at one point, iirc.
ah, i see i think i misinterpreted the "And REBL?" remark -- it seems like it's not usually hard to add socket-based repl functionality to something.