Fork me on GitHub
#shadow-cljs
<
2017-11-04
>
thheller07:11:58

both kinda, it will not generate any externs for everything it warns about

thheller07:11:14

but things it doesn’t warn about will be generated

thheller07:11:24

regardless of warn-on-infer

mhuebert11:11:16

Are there things it will generate externs for silently, but then not generate with warn-on-infer?

mhuebert11:11:46

I guess the thing to avoid is a setting that could cause warnings to replace extern-generation on namespaces the user doesn't control?

thheller11:11:07

the only bad thing *warn-on-infer* can do is cause too many warnings

thheller11:11:36

and it can generate LOTS of warnings, 600+ in cljs.core alone

thheller11:11:47

that is after I tweaked it a lot, 1000+ before

thheller12:11:26

I guess enabling it be default would push more people towards tagging with ^js

thheller12:11:56

the only problem is that sometimes the ^js tag is incorrect and should actually be tagged as ^clj

thheller12:11:33

well .. rather rarely actually so it should be ok

thheller12:11:34

dunno .. I will leave it manual for now, maybe add a config option later that defaults to false at first

thheller13:11:37

@mhuebert I just added shadow-cljs pom which IntelliJ/Cursive can import. basically the same as writing the “fake” project.clj. still better to use project.clj if you want to publish libs and such though.