This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-01-26
Channels
- # announcements (1)
- # asami (7)
- # aws (3)
- # babashka (30)
- # beginners (21)
- # calva (48)
- # cider (11)
- # clj-commons (5)
- # clj-kondo (12)
- # cljdoc (5)
- # cljfx (1)
- # cljs-dev (32)
- # cljsrn (4)
- # clojure (218)
- # clojure-europe (88)
- # clojure-nl (11)
- # clojure-uk (31)
- # clojurescript (8)
- # cursive (98)
- # data-science (6)
- # datomic (49)
- # emacs (12)
- # events (4)
- # fulcro (47)
- # graalvm (3)
- # graphql (4)
- # introduce-yourself (5)
- # java (13)
- # juxt (9)
- # lsp (74)
- # meander (3)
- # membrane (4)
- # missionary (31)
- # off-topic (24)
- # pathom (41)
- # portal (4)
- # reagent (3)
- # releases (1)
- # remote-jobs (3)
- # rewrite-clj (4)
- # shadow-cljs (10)
- # slack-help (2)
- # testing (20)
- # tools-deps (43)
Working through the nonsense above i made an example annotation processor to use as a demo
i didn’t need any - i just wanted to have an example project that compiled and packaged one up right
but I do need help if you know how to properly carry over annotations in generated code, just to make that library workable
the most basic one is TYPE_USE annotations like
@Target(TYPE_USE)
@interface ABC {}
class Ex {
@ABC List<@ABC String> fieldName;
}
Which needs to turn in to
[email protected] List<[email protected] String>
In my generated codebut currently turns into
@ABC java.util.List<@ABC java.lang.String>
Which is wrong and doesnt compilebut i turns out something is broken in the universe and there weren’t like a million hello world annotation processors like this