Hi, I could not seem to find the exclude mechanism for ignoring java.lang.* e.g. (Integer/parseInt numstr)
, any clues appreciated
@gmercer please give a full standalone repro and then the expected outcome
@borkdude I just cloned https://github.com/mogenslund/liquid and ran clj-kondo --lint src/liq/editor.cljc
It is a cljc so this command removes the warning cat src/liq/editor.cljc | clj-kondo --lang clj --lint -
If it’s cljc Java interop should not occur outside of branches
Unless it targets a different runtime than JVM and JS
ahh - I see
sorry - for what looks like cross-posting - but they were slightly different problems (in my mind)
PS really enjoying your latest videos .. I was wondering about a bb/graalvm version of liquid .. which requires some understanding of sci+graal, any chance of a video on that topic?
e.g. a tiny project that you could show is not sci compatible, the slight changes to make it so and how that can be graal'd
@gmercer You need sci if you need eval
in your program. If you don't need this, you can possibly just compile it with GraalVM as is
I'm not sure what it entails to compile liquid to graalvm. What does it use for UI?
java.awt
. That should maybe work on GraalVM 21 and only on linux: https://medium.com/graalvm/graalvm-21-0-introducing-a-new-way-to-run-java-df894256de28
@gmercer The main incompatibility with sci and clojure is the absence of deftype
and definterface
and some edge cases around defprotocol
and reify
@borkdude liquid is a zero dependency text based vim/emacs mash - beware it may leave you terminal a bit wonky, definitely worth a try
What do you think about a linter that warns if you are using a var/ns from a dep that is marked with :no-doc
?
@lee That seems interesting, but clj-kondo doesn't know what is a dep and what is your own source
yah, was describing in the abstract, you’d have to tell it to exclude your nses.
BTW, liking your vids @borkdude! If I hadn’t chosen to be a frugally retired hobbyist, I’d certainly be sponsoring you (and others). Hopefully my contributions in other areas in some small way make up for my lack of $ sponsorship!
It sure does, don't worry :)
I’d love to see you be able to afford to do OSS as your main job!
I've also mean meaning to do something like this for vars from .impl
namespaces. Let's think more about it. But first: dinner.
Bon appetit!
@juhoteperi Thanks for sponsoring me on Github! Would you like access to the private sponsors channel?
Thanks! Sure.