This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-10-01
Channels
- # aws (37)
- # babashka (7)
- # babashka-sci-dev (2)
- # beginners (75)
- # biff (7)
- # calva (85)
- # cider (9)
- # clj-kondo (26)
- # clj-yaml (1)
- # clojure (45)
- # clojure-europe (4)
- # clojure-norway (1)
- # clojure-spec (3)
- # clojure-uk (2)
- # clojurescript (3)
- # core-typed (2)
- # cursive (12)
- # fulcro (3)
- # humbleui (5)
- # jobs (8)
- # malli (1)
- # meander (3)
- # membrane (1)
- # portal (50)
- # squint (15)
- # vim (1)
Is there a way to disable Cursive’s built-in linting? I work on Aleph, which uses many funky potemkin macros, and I’m trying to cut down on the number of false positives I see. I’ve sort of got kondo configured to the point where it’s ignoring what I want it to, but I’m still getting a lot of spurious warnings from Cursive itself. (The “resolve as” functionality doesn’t cut it.)
Could also use #clj-extras-plugin to get better clj-kondo support within cursive
I’ll take a look at Aleph again, back in the day I did add support for Potemkin, but perhaps that got broken.
Thanks, Noah, I already use it. The issue is kondo now understands certain Potemkin things correctly, but Cursive doesn’t, so I need to disable its linting.
@U10EC98F5 Just to be clear, do you get these errors when writing apps which use Aleph, or when working on Aleph itself?
Working on Aleph itself. I’m the current maintainer
Along with a couple others.
Hmm, yeah, it’s possible that might not work as well - I did put some effort into ensuring that projects using Aleph would work. I’ll take a look at Aleph them.
FWIW, there’s a few proto-potemkin fns/macros here and there in Zach’s codebase, and they’re not always the same 😬 as the potemkin versions.